I was using star9 0.4.0.0 and had configured Bitcoin ZeroMQ and RPC
by following How To - Exposing electrs and bitcoind over LAN in StartOS 0.3
I am using Bitcoin ZeroMQ and RPC from python script and all was fine for last 5-6 months
today, after update to 0.4.0.1 Bitcoin ZeroMQ and RPC are not working any more
I have seen that UI has changed a lot
and I am running Bitcoin Knots #knots:29.3.1:16
In Services → Bitcoin Knots → Interfaces → RPC
I have https://192.168.1.110:55888 and “nc 192.168.1.110 55888“ is working fine
but not from python script (same for ZeroMQ)
python script uses python-bitcoinrpc==1.0
I have also created RPC user in Services → Bitcoin Knots → Auctions & Config → RPC Users → Generate RPC User Credentials
and tried to use thous credentials, but no luck
this is what was working on star9 0.4.0.0
rpc = “btcstandup://bitcoin:RPC_PASSWORD_HERE@EXTREMELYLONGONIONADDRESS.local:8332”
zeromq = “tcp://EXTREMELYLONGONIONADDRESS.local:28332”
I have tried with new RPC user and password, with direct IP, port change
but it is not work
currently I am trying to get RPC to work, hoping when I figure that out it will be easier with ZeroMQ
best luck I had with
rpc = “btcstandup://bitcoin:RPC_PASSWORD_HERE@192.168.1.110:55888”
and
rpc = “http ://bitcoin:RPC_PASSWORD_HERE@192.168.1.110:55888” (had to put space, so not to have waring of 2 links per new user)
but both give same error
.venv/lib/python3.13/site-packages/bitcoinrpc/authpr
oxy.py", line 186, in _get_response
raise JSONRPCException({
‘code’: -342, ‘message’: ‘non-JSON HTTP response with \’%i %s\’ from server’ % (http_response.status, http_response.r
eason)})
bitcoinrpc.authproxy.JSONRPCException: -342: non-JSON HTTP response with ‘307 Temporary Redirect’ from server
on docs.start9DOTcom I do not see documentation for 0.4.0.1
hope that somebody have same problem and did figured it out
Thanks