-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket Hangups for RPC calls #51
Comments
@agustinkassis This is likely a RPC API version issue. This tool does not identify what version of node it's connected to and therefore doesn't tailor itself to RPC API differences between versions. May I ask: what version of Bitcoin Core are you running? |
It was verison 1.6.2, recently updated to 1.6.3. Those API commands are available. |
Having this problem as well. |
@agustinkassis @ConanDW It's been a long time, so not sure if you're still interested or working on getting this tool configured, but if so, I have another question: is your node configured to accept RPC requests from the host running btc-rpc-explorer? This would be done via "rpcallowip" configurations for your node. Also, I'm assuming that your node version was 0.16.2 and upgraded to 0.16.3? |
Happy to reopen if I hear back. |
Hello @janoside, I see it's been a few years since this issue was reported but I was "lucky" enough to run into it, too. I'm using Node v18.16.0 LTS with BTC Core 24.0.1. Not really sure what to do, I'll try to downgrade to Node 16 but other than that I'm out of ideas. Wanted to mention it here if anyone else ran into it on those versions. |
While trying to access http://localhost:8332
I get the following error and unable to access the website through browser.
The text was updated successfully, but these errors were encountered: