-
Notifications
You must be signed in to change notification settings - Fork 179
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
Directory nodes not working #1691
Comments
|
@kristapsk, indeed I've tried all of them, but none is working: #directory_nodes = g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222,3kxw6lf5vf6y26emzwgibzhrzhmhqiw6ekrek3nqfjjmhwznb2moonad.onion:5222,bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222 |
What is the error you are getting? As some of these dnodes are working for me. |
Here a log:
I'm using it in a docker but it should not be the issue as I can correctly reach both bitcoin core and tor from the container. |
@kristapsk, which one exactly is working for you? I would like to try to debug the issue. Thanks! |
|
Hello,
I don't know if I'm missing something, but I've just setup everything in a docker instance but apparently all the default directory nodes, defined in the configuration file as directory_nodes, are not reachable.
There are other public directory nodes that I can use?
The text was updated successfully, but these errors were encountered: