search

chaeplin / dashmnb

run dash masternode(s) with hardware wallet. dashmnb simplify local cold wallet part.
MIT License
15 stars 5 forks source link

401 unauthorized during check sync status #42

Closed msbeck closed 7 years ago

msbeck commented 7 years ago

I'm getting the following response when I run dashmnb.py using port 9998: `Network : MAINNET --> get dash explorer block count --> get dashd status

--> checking syncing status

version : 0.3.rc8 caller : check_dashd_syncing function : rpcgetinfo err : ("non-JSON HTTP response with '401 Unauthorized' from server",) ===> Dash-QT or dashd running ?`

Is this a 401 from my local Dash-QT to dashmnb, or a 401 from my remote node server to my local Dash-QT?

chaeplin commented 7 years ago

with get dashd status, dashmnb uses local or remote dashd.

1) if dashd is local(127.0.0.1), check rpcuser and rpcpassword(config.py and dash.conf of dashd) 2) if dashd is remote(ssh tunnel), check ssh tunnel and check rpcuser and rpcpassword(config.py and dash.conf of dashd)

---> https://github.com/chaeplin/dashmnb/blob/master/dashlib/config.sample.mainnet.py

3) you can use my remote rpvsvc ---> https://github.com/chaeplin/dashmnb/blob/master/dashlib/config.sample.mainnet.remotesvc.py

msbeck commented 7 years ago

Thanks. Although the rcpuser and password can vary from the local Dash-QT and the server, the dashmnb script and Dash-QT need to match. Those are matched up and auth occurred. Waiting for a re-index now. Thanks.