I have the dogecoin daemon running successfully on Ubuntu, started with this command:
It's listening on port 22556, as verified by netstat.
I can also pass commands to it directly via the Ubuntu terminal, like so:
However, passing RPC requests to it through HTTP does not work. The daemon doesn't refuse the connection (and I can verify that it does refuse the connection if I use a port other than 22556); instead, the connection hangs, with no data being sent to the client making the HTTP request. Directly connecting to
makes the web browser sit and wait for data. Similarly, making an RPC request via a PHP script, and then accessing that script in a browser, makes the browser wait for 30 second before PHP spits out an error stating that the maximum execution time of 30 seconds was exceeded.
I have my ~/.dogecoin/dogecoin.conf file as such:
server=1 rpcuser=a rpcpassword=b
(I know the username and password I typed there are insecure; those are temporary until I can at least make a connection.)
I've tried adding the line
to the end of the config file, but that didn't change the behavior at all.
What am I doing wrong -- why isn't my Dogecoin daemon accepting RPC requests (or any from-an-actual-browser HTTP requests, for that matter)?
edit: Also, I can verify that the daemon is caught up with the blockchain.