-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Private reachability for Public node #3087
Comments
The node may be behind a firewall. Is it possible to enable prometheus metrics? |
Yes, we do have a firewall for security reasons, but we have enabled all the ports we are aware of.
Sure, I just enabled it, and I believe this is what you're looking for: Prometheus Metrics. |
You need to open the port that the node is listening on. From the metrics, I see a lot of your requested dailbacks errored. I also see that in the last few hours, the node has not made any dial back requests, which is very strange because I see some peers in swarm. Maybe none of them support autonat protocol? If you're confident that the node is private, you can use https://github.com/libp2p/go-libp2p/blob/master/options.go#L349 |
Thanks for time to check and identify the issue. Please consider these is not a test network and we can't easily make any changes for debugged purpose. |
Which port? |
Probably we have at least 6 (The nodes we have configured) |
The port is determined based on how you configure the libp2p host. For example, this is how you listen on port 9000 go-libp2p/examples/libp2p-host/host.go Lines 60 to 63 in 4e85c96
|
Reachability is not consistent information, and for some unknown reason, some public nodes with public IPs are shown as private [Example here].
Any idea why this happens? Probably, this may have some effects on other modules, which I believe should be taken care of.
The text was updated successfully, but these errors were encountered: