-
Notifications
You must be signed in to change notification settings - Fork 194
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
RPCAuth Support #55
Comments
My understanding is that rpcauth changes how you set up the wallet config file by removing the Back on the block explorer side you still provide the same rpc username as always and the rpc password should be the plaintext password, not the hashed password. Perhaps this is where you are going wrong by trying to use the hashed password? Give that a try and if it still doesn't work, can you share the error msg you are seeing and which coin you are trying to connect to the explorer? |
ok so far even that in config not use that still support this explorer? since conf using rpcauth. pivx coin |
First of all, the explorer doesn't yet support the zerocoin or SHIELD transactions that PIVX uses. If you are trying to sync the actual Pivx blockchain as opposed to a clone or fork which never used private transactions then you will undoubtedly have problems with those private transactions not adding up correctly or other weird behavior unless you plan to add support for those protocols yourself. But as far as I'm aware, the rpcauth changes in the config file for PIVX and other coins have no effect on the explorer and you can continue to enter the rpc user and password in the explorer config as you would for any other coin and it should work fine. Make sure you are using the plaintext rpc password in the explorer config and not the hashed password that you would use for the rpcauth line in the wallet config file. Also, a common mistake that is made when trying to connect the explorer to your coin wallet is that you might be using the wrong port #. Make sure you are using the correct rpc port # and not the p2p port #. If you still continue having problems, are you trying to connect the actual PIVX coin to the explorer or is it another coin that was cloned from PIVX so I can test it on my end to make sure the connection works. Also, can you share what error msg you are seeing in the console? |
This not support RPC Auth?as we know bitcoin and newer blockchain model of dash,pivx is already deprecated using rpcuser and rpcpassword. If possible this enable rpcauth.
Note : this suggestion for secures
The text was updated successfully, but these errors were encountered: