-
Notifications
You must be signed in to change notification settings - Fork 12
Troubleshooting Connection Problems
Dominik Renzel edited this page Apr 20, 2015
·
2 revisions
If your node startup fails with messages like "Could not connect" or "All bootstraps are faulty" please go threw the following checklist:
- TCP AND UDP must be allowed to pass your firewall ports used by the node (usually 9011, 9085 or similar)
- DNS is provided and allowed to be used by the LAS2peer instance
This means local restricted networks including networks behind NATs and/or firewalls, but with no connection to the internet. Usually found at home or inside institute networks.
- verify that firewall_test_policy = never and nat_search_policy = never are specified inside the pastry node configuration file.
This means at least more than 5% of the nodes inside the network are reachable over the internet.
To configure a node running inside your home network (NAT and firewall) please see our detailed article, here.
This means you have a node running inside a cloud solution with NAT, but no port forwarding requirement.
- verify that external_address = 123.45.67.89:1234 is specified inside the pastry node configuration file.