I’ve downloaded and put in and received up and operating a bitcoin core node, and it’s operating nice so far as individuals are connecting to it on port 8333 simply nice. Nevertheless I can not appear to connect with it myself on the identical machine utilizing python bitcoinrpc library…
My .conf information appears to be like like…
port=8333
timeout=10000
printtoconsole=1
chain=principal
rpcuser=one
rpcport=8334
#rpcauth=one:xxxxxx
server=1
coinstatsindex=1
daemon=1
txindex=1
and my python app..
from bitcoinrpc.authproxy import AuthServiceProxy, JSONRPCException
# rpc_user and rpc_password are set within the bitcoin.conf file
rpc_user = "one"
rpc_password = "two"
rpc_connection = AuthServiceProxy("http://%s:%[email protected]:8334"%("one","two"))
best_block_hash = rpc_connection.getbestblockhash()
And when it runs it fails on line
best_block_hash = rpc_connection.getbestblockhash()
with the next error…
Traceback (most up-to-date name final):
File ".bitcoin104.py", line 10, in <module>
best_block_hash = rpc_connection.getbestblockhash()
File "D:PROJECTSpython38_env_bitcoin.venvlibsite-packagesbitcoinrpcauthproxy.py", line 139, in __call__
response = self._get_response()
File "D:PROJECTSpython38_env_bitcoin.venvlibsite-packagesbitcoinrpcauthproxy.py", line 179, in _get_response
http_response = self.__conn.getresponse()
File "c:usershansoappdatalocalprogramspythonpython38libhttpclient.py", line 1344, in getresponse
response.start()
File "c:usershansoappdatalocalprogramspythonpython38libhttpclient.py", line 307, in start
model, standing, cause = self._read_status()
File "c:usershansoappdatalocalprogramspythonpython38libhttpclient.py", line 276, in _read_status
increase RemoteDisconnected("Distant finish closed connection with out"
http.shopper.RemoteDisconnected: Distant finish closed connection with out response
I’ve checked all my ports, and I’m sure they’re working, they work by telnet, the netstat -a exhibits the ports are listening when i open the bitcoin core node, and when i attempt a unique port I get a unique error complaining about host connection was refused. So I’m 99% sure the port forwarding and firewall is open to the specified ports. Port 8333 for out of doors connections exhibits a log of individuals connecting to the server. So I’m virtually sure it isn’t the machine, firewall, or router not permitting connections by the port.
That leaves both one thing I’m organising incorrect with the password. I modified the setup to make use of a easy one, two useid and password for testing, and so I can publish right here to indicate precisely what I’m doing phrase for phrase within the conf and the python script.
I’m actually pounding my head in opposition to the wall.. Is it attainable one thing to do with rpcauth… i attempted operating that and making a hash after which tried to make use of that as a alternative in my http://cross:[email protected],1:8334 connection. Nevertheless it doesnt’ appear to work both. However humorous sufficient once I kind the clearly incorrect password in i get the identical error I get now. But when I alter say the ip tackle then it fails up on the AuthServiceProxy creation line as a substitute. And the difficulty says that the machine host refused connection. So all this factors to the node node liking my userid and/or password however I can not discover any examples to know for certain I’m setting these up accurately for the node within the .conf file earlier than launching node, or if i’m doing one thing incorrect within the python script?
