This repository has been archived by the owner on Nov 15, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 192
Privatenet fails to initialize #1012
Comments
I think the discussion here is; should we change the default port of |
@ixje perhaps this could be improved with better documentation in https://github.com/CityOfZion/neo-privatenet-docker. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior
When trying to run neo-python using a privatenet, the program hangs and I receive the follow error after exiting using "Ctrl-C":
After troubleshooting and receiving advice on Slack, @hal0x2328 led to me a solution: changing the nodeport in the json file to something other than 20333.
This is an issue because anyone running the docker image for the privatenet on the same workstation they are using neo-python will run into this problem.
The default
protocol.privnet.json
listsAnd the
Nodeport
as 20333.Ref: https://github.com/CityOfZion/neo-python/blob/master/neo/data/protocol.privnet.json
Expected behavior
Using the docker image and
np-prompt -p
, a user should be able to access a privatenet without additional work.How to reproduce
venv
if applicablenp-prompt -p
Your environment
Let us know in what environment you're running into the issue:
The text was updated successfully, but these errors were encountered: