You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node is located behind NAT with 80 port forwarding from public IP to private. From the Internet - node is available, but when checking the Node URI Health Check an error appears and the node is down. I additionally configure NAT Loopback (Hairpin NAT / NAT Reflection) to solve this problem. Not every hardware and software supports it. It would be nice to add an option to disable Node URI Health Check in the settings.
The text was updated successfully, but these errors were encountered:
Running a Node behind NAT is not really encouraged. It would mostly apply to those who are trying to run a Node on a home Internet connection which is sub-optimal from a performance and reliability standpoint. We'll consider this, but no promises.
Node is located behind NAT with 80 port forwarding from public IP to private. From the Internet - node is available, but when checking the Node URI Health Check an error appears and the node is down. I additionally configure NAT Loopback (Hairpin NAT / NAT Reflection) to solve this problem. Not every hardware and software supports it. It would be nice to add an option to disable Node URI Health Check in the settings.
The text was updated successfully, but these errors were encountered: