Forum Replies Created

Viewing 15 replies - 436 through 450 (of 492 total)
  • Plugin Author dashed-slug.net

    (@dashedslug)

    @toursumo Can you please give me more information? There is some debug info in the dashboard that you could paste here.

    Also, if you want to try the solution described above, these are the SQL commands for creating the table manually. Just change ccmd_ to wp_ or whatever your table prefix is. If any of these commands gives you an error, that will let me know what’s going on.

    Finally, if you can enable the logs, and check what is written after you activate the plugin. If you can do that, it will help me the most.

    thank you
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    OK I have tested the plugin version 2.8.2 on a clean setup with PHP 5.3.29 and the latest WordPress. The tables are created on my end. However I did not test with your exact database setup. Instead I used MySQL5.5.53.

    There are a couple of things you could do:

    1. Inspect the log files. This could tell us what went wrong. However there will also be some SQL errors in there that are to be expected.

    2. Try creating the tables manually. If there is some incompatibility with your system, it might become apparent. Try the following in your SQL console:

    CREATE TABLE ccmd_wallets_txs (
    id int(10) UNSIGNED NOT NULL,
    blog_id bigint(20) NOT NULL DEFAULT ‘1’ COMMENT ‘blog_id for multisite installs’,
    category enum(‘deposit’,’move’,’withdraw’) COLLATE utf8mb4_unicode_520_ci NOT NULL COMMENT ‘type of transaction’,
    tags varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ” COMMENT ‘space separated list of tags, slugs, etc that further describe the type of transaction’,
    account bigint(20) UNSIGNED NOT NULL COMMENT ‘ccmd_users.ID’,
    other_account bigint(20) UNSIGNED DEFAULT NULL COMMENT ‘ccmd_users.ID when category==move’,
    address varchar(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL DEFAULT ” COMMENT ‘blockchain address when category==deposit or category==withdraw’,
    txid varchar(255) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL COMMENT ‘blockchain transaction id’,
    symbol varchar(5) COLLATE utf8mb4_unicode_520_ci NOT NULL COMMENT ‘coin symbol (e.g. BTC for Bitcoin)’,
    amount decimal(20,10) NOT NULL COMMENT ‘amount plus any fees deducted from account’,
    fee decimal(20,10) NOT NULL DEFAULT ‘0.0000000000’ COMMENT ‘fees deducted from account’,
    comment text COLLATE utf8mb4_unicode_520_ci COMMENT ‘transaction comment’,
    created_time datetime NOT NULL COMMENT ‘when transaction was entered into the system in GMT’,
    updated_time datetime NOT NULL COMMENT ‘when transaction was last updated in GMT (e.g. for update to confirmations count)’,
    confirmations mediumint(8) UNSIGNED DEFAULT ‘0’ COMMENT ‘amount of confirmations received from blockchain, or null for category==move’,
    status enum(‘unconfirmed’,’pending’,’done’,’failed’,’cancelled’) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ‘unconfirmed’ COMMENT ‘state of transaction’,
    retries tinyint(3) UNSIGNED NOT NULL DEFAULT ‘1’ COMMENT ‘retries left before a pending transaction status becomes failed’,
    admin_confirm tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if an admin has confirmed this transaction’,
    user_confirm tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if the user has confirmed this transaction over email’,
    nonce char(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL COMMENT ‘nonce for user to confirm via emailed link’,
    extra varchar(255) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL COMMENT ‘extra info required by some coins such as XMR’
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

    ALTER TABLE ccmd_wallets_txs
    ADD PRIMARY KEY (id),
    ADD UNIQUE KEY uq_tx_idx (txid,symbol),
    ADD KEY account_idx (account),
    ADD KEY blogid_idx (blog_id);

    CREATE TABLE ccmd_wallets_adds (
    id int(10) UNSIGNED NOT NULL,
    blog_id bigint(20) NOT NULL DEFAULT ‘1’ COMMENT ‘blog_id for multisite installs’,
    account bigint(20) UNSIGNED NOT NULL COMMENT ‘ccmd_users.ID’,
    symbol varchar(5) COLLATE latin1_bin NOT NULL COMMENT ‘coin symbol (e.g. BTC for Bitcoin)’,
    address varchar(255) COLLATE latin1_bin NOT NULL,
    created_time datetime NOT NULL COMMENT ‘when address was requested in GMT’,
    extra varchar(255) COLLATE latin1_bin NOT NULL DEFAULT ” COMMENT ‘extra info required by some coins such as XMR’
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin;

    ALTER TABLE ccmd_wallets_adds
    ADD PRIMARY KEY (id),
    ADD UNIQUE KEY uq_ad_idx (address,symbol,extra),
    ADD KEY retrieve_idx (account,symbol),
    ADD KEY lookup_idx (address);

    Let me know what you find.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thanks for reporting,

    I will investigate and let you know soon.

    regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thanks John it was a pleasure.

    I will update the plugin so it will recommend the correct netmask setting in the next version.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Solved. Solution involved adding the netmask to the rpcallowip argument.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Also, if your IP is 1.2.3.4, try adding a netmask, such as:

    rpcallowip=1.2.3.4/24.

    Let me know if it works.

    Plugin Author dashed-slug.net

    (@dashedslug)

    You can send me your conf file in the email, [email protected] so I can have a look. The core client also returns 403 if your rpcallowip is not correct, so check that too. It should be set to the IP of your WordPress VPS.

    Plugin Author dashed-slug.net

    (@dashedslug)

    What version of Bitcoin core are you trying to connect to?

    Plugin Author dashed-slug.net

    (@dashedslug)

    OK,
    since you are receiving a 403 error from your wallet, you can stop looking at connectivity issues. The plugin is connecting to your wallet fine, and is returning an authorization error.

    The video is somewhat dated and I’m planning an update. Here’s what you can do now:

    First, check to make sure that you have entered the same username and password in your adapter settings and .conf file. Once you enter a password in the adapter settings, the instructions for what to add to the conf file will reflect the change in the rpcauth= line, which contains a salted version of your password. That is, make sure that you have copied and pasted the config settings *after* you have first saved the password in the plugin.

    Second, if that does not work for whatever reason, you can try to enter your password as cleartext in the config. Remove the rpcauth= line and add the two rpcuser= and rpcpass= lines. The documentation for conf files is here in case you want to have a look: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File

    Check these two things and let me know how it goes.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    This sounds like a connectivity issue.

    First, please have a look at the adapter status under “adapters”. There might be some useful info there.

    You could also enabled logging and check your debug.log. Instructions for enabling debugging in WordPress can be found here https://codex.ww.wp.xz.cn/Debugging_in_WordPress

    Also, try your connectivity via a shell using nc or telnet to make sure the port is accessible between machines. Just because you are not running a firewall does not mean that a firewall does not exist between your VPSs.

    Let me know what you find.

    best regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you.

    And yes, let me know.

    best regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hi and thanks for the suggestion. The idea is indeed simple and has been requested before, the implementation however is not. This would have to evolve into an extension that manages escrow over advertised services. This might indeed be implemented some day.

    Another approach would be to take an existing system that manages a freelance marketplace and add the feature on top, interfacing to the wallets API as needed.

    I do not have the time to develop this at the moment, but I will add it to the list of ideas for future extensions.

    Again, thank you for suggesting this. It is a good idea.

    regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    If you do not know much about setting up a stand-alone wallet then it is probably not a good idea to run and maintain one. Please have a look at the FAQ section under “I am having trouble with the bitcoin.conf file”. Essentially you would be better off considering the cloud wallet adapters, either CoinPayments or block.io.

    If on the other hand you do wish to proceed with manual installation of bitcoin on a server, you can have a look at https://bitcoin.org/en/full-node for detailed instructions. First consider the disk and bandwidth requirements before installing a Bitcoin core node.

    regards,
    Alex

    best regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Happy to help.

    Plugin Author dashed-slug.net

    (@dashedslug)

    You need to provide the following:

    Public key
    Private key
    Merchant ID
    IPN secret

    Do not enter any domain, only the IPN secret as set in your CoinPayments settings. This is step 6 in the instructions.

    If you have already done this, then simply wait out the two minutes and try again. This could be an one-off error. Their API throttles errors but errors are caused every time they introduce new coins with various peculiarities.

    I am testing the adapter right now and do not see any problem, so please try again.

    Let me know how it goes.

Viewing 15 replies - 436 through 450 (of 492 total)