Please Help - Bitcoin-core (bitcoind) and Ubuntu VPS / Web Front-end

[timmytim]

Hey all.

I purchased Eckmar's market script from the marketplace and I got the website portion up and running without any issues. I am, however unable to get anything bitcoin related working.

I am using an Ubuntu 16.04 x64 VPS from Digital Ocean. 2 vCPU and 2GB RAM.

I installed bitcoin core on the same server using apt and I have added a bitcoin.conf which is pruning the node and also defines an rpcuser and password. I have also set it as a daemon and server.


My Issue:
----------------

When I start the bitcoin server it works fine, no errors on screen or in the log file in ./bitcoin. I can run bitcoin-cli commands from Putty all day long also with no issues.

In the market script, when I try to get a new address to send btc to or check a balance, that's when it doesn't work. The script is making json / rpc calls using bitcoin-cli but it simply isn't working. Nothing happens and there is nothing that I can see in the logs as to the actual problem. There are no errors.

I am willing to pay someone to help me fix this. I need this script up and running ASAP. Please PM me here if you can help. If you have any ideas to try, please let me know below. I am eager to get this going.

[tspacepilot]

I'm not familiar with this market script.  But did you check the port your bitcoind is listening on is the same one that your market script is sending on?  (I guess I'm assuming a tcp/ip communication channel)

In general, can you create (or read from) logs on both ends to see what's going on?  If your bitcoind isn't responding at all to the market script, can you log whether you got any reply at all?

Just some ideas.

You say you can issue bitcoin-cli commands all day, so double check the port password, rpcuser, etc from your bitcoin.conf are the same values your market script is using.

[timmytim]

Thanks for your reply.

The market has a .env file in the root of the script that specifies port 18333 for bitcoind by default but I changed it to 8332 based on the easybitcoin.php set in those config files. I assumed that is what I should use for bitcoind since that is what was in use for easybitcoin. Either way, the ports being changed around didn't matter.

I thought maybe this was a firewall issue with Digital Ocean so I made a virtual firewall on there and opened those ports but it also didn't have any effect.

I am a Microsoft / IIS guy by trade and Linux / Nginx log files are something that I would have to research a bit to find... on the php side. To my knowledge the market script doesn't log but I will double-check to make sure.

[tspacepilot]

So, in your firewall, are you doing nat to map 18333 to 8332?  If one program is listening on a different port than the other is sending on then that seems like the place to look.

Again, sorry this is so general, I don't know your script.  On GNU/Linux, you generally find logs for system programs in /var/log/.  I've used apache more than nginx, so /var/log/apache2/ for those logs.  nginx may be in /var/log/nginx (that's where I'd look).  I suppose I was thinking more about just debugging using echo >> somelogfile in your php program.  And, since it's been a while since I messed with bitcoin rpc, I can't remember if/where rpc logs are but maybe in ~/.bitcoin/debug.log