-
Notifications
You must be signed in to change notification settings - Fork 32
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
docker-compose dynamic IP problem #16
Comments
Ran into this issue on various Ubuntu VM's and haven't been able to get the repo to work as intended due to it. Wonder if there is a workaround that anybody has found. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Branch: master.
I reduce the numbers of authority servers to reproduce the problem clearly.
Build it with the new up command with --scale flag(leave client offline now).
da1 log output shows the server starts correctly.
Restart the services.
da log output shows that the dynamic ip address of the scale command confuses the authority server.
Suppose client joins the private network now.
Socks port is already opened.
Connection is blocked here.
Maybe the scale command is not suitable for building a private tor network here until it can persist the network status.
Thank you for reading.
The text was updated successfully, but these errors were encountered: