Topic: Can't access bitcoin node (Read 949 times)
If you haven't set a rpcport in the bitcoin.conf file the default is 8333 not 8332. Give that a go and see if it works.
think when using rpc it uses the port you set with
in the .conf file you should have
(think its the right command)
so rpc would listen on 8333 not 8332 (or what ever port you want
in the .conf file you should have
Code:
rpcport=8333
(think its the right command)
so rpc would listen on 8333 not 8332 (or what ever port you want
I have a raspberry pi (with a static ip) that is connected to a windows desktop via ethernet. On my windows desktop, I am running an instance of bitcoin-qt, and I am trying to access this.
First, I looked up my desktop's ip address using ipconfig, which turned out to be 192.168.0.18. Since I have an apache web server on my desktop as well, I curl'd it from the raspberry to test that the ip was indeed correct.
Next, I tried to curl my desktop on port 8332 (which is where bitcoin-qt is listening) with the correct credinals. It gave me a "forbidden" message.
I double checked my firewall to make sure that wasn't the problem. I also checked my rpcallowip to make sure my raspberry wasn't being blocked there.
I then went onto my desktop and curl'd localhost port 8332 from there. I got a json output, as expected. Curl'ing 192.168.0.18 on port 8332 still gave me a forbidden message.
Does anybody have any idea what is going on?
First, I looked up my desktop's ip address using ipconfig, which turned out to be 192.168.0.18. Since I have an apache web server on my desktop as well, I curl'd it from the raspberry to test that the ip was indeed correct.
Next, I tried to curl my desktop on port 8332 (which is where bitcoin-qt is listening) with the correct credinals. It gave me a "forbidden" message.
I double checked my firewall to make sure that wasn't the problem. I also checked my rpcallowip to make sure my raspberry wasn't being blocked there.
I then went onto my desktop and curl'd localhost port 8332 from there. I got a json output, as expected. Curl'ing 192.168.0.18 on port 8332 still gave me a forbidden message.
Does anybody have any idea what is going on?
Jump to: