-
Notifications
You must be signed in to change notification settings - Fork 18
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
error: Could not connect to the server 127.0.0.1:8331 (error code 1 - "EOF reached") on openbsd #17
Comments
Hi, sorry for not replying to your e-mail, last couple of days were terrible. One more thing that comes to my mind is try to use cookie authentication. Maybe we've screwed up password authentication and I'm not sure if anyone actually tested it, since cookie files are better. Although the code looks correct from what I can tell. |
no problem at all, thought so, maybe someone else can help or has already had the same problem i tried in the config is that what you meant with using the cookie authentication? |
Did you set |
yes |
Could you run Wireshark or a similar tool to catch streams of those apps communicating? Ideally catch both bitcoin-cli -> btc-rpc-proxy and btc-rpc-proxy -> bitcoind; possibly also bitcoin-cli -> bitcoind Don't forget to censor authentication if you post it, but also compare if latter two match. |
i never used wireshark - this is what i get using tshark (the command line tool of wireshark): bitcoin-cli -> btc-rpc-proxy
btc-rpc-proxy -> bitcoind
bitcoin-cli -> bitcoind
no clue where i should have censored here something, but i just used throwaway username and password for the requests and apperently the latter two don't match |
That looks like some kind of high-level overview of packets. Wireshark has "follow TCP stream" feature which is needed - it shows directly data (bytes) transferred. |
bitcoin-cli -> btc-rpc-proxy
btc-rpc-proxy -> bitcoind
bitcoin-cli -> bitcoind
|
cargo run --release -- --conf btc_rpc_proxy.toml
with:bitcoin-cli -rpcuser=test -rpcpassword=test -rpcport=8331 getmininginfo
:error: Could not connect to the server 127.0.0.1:8331 (error code 1 - "EOF reached") Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
the proxy is running cause
netstat -na -f inet | grep 8331
gives me:of course when i run
bitcoin-cli -rpcuser=nathanael -rpcpassword=[redacted] getmininginfo
it works (using the values inserted in the config file of btc-rpcy-proxy seen above)has anyone an idea what i am doing wrong? something to do with openbsd?
The text was updated successfully, but these errors were encountered: