I’ve downloaded and put in and acquired up and operating a bitcoin core node, and it’s operating effective so far as individuals are connecting to it on port 8333 simply effective. 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=major
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
    elevate 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 via telnet, the netstat -a reveals the ports are listening when i open the bitcoin core node, and when i strive 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 reveals a log of individuals connecting to the server. So I’m nearly sure it isn’t the machine, firewall, or router not permitting connections via the port.

That leaves both one thing I’m establishing fallacious with the password. I modified the setup to make use of a easy one, two useid and password for testing, and so I can put up right here to point out 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 doable one thing to do with rpcauth… i attempted operating that and making a hash after which tried to make use of that as a substitute in my http://cross:[email protected],1:8334 connection. But it surely doesnt’ appear to work both. However humorous sufficient once I sort the clearly fallacious password in i get the identical error I get now. But when I modify say the ip tackle then it fails up on the AuthServiceProxy creation line as an alternative. 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 appropriately for the node within the .conf file earlier than launching node, or if i’m doing one thing fallacious within the python script?