autumn crow
Good morning,
I currently have a problem when I try to access the panel from outside my home, port 80 is wrong. I have access to the web interface but I cannot do any other interaction locally. works well if someone has an idea where the problem could come from I'm interested
floral heartBOT
Make sure that your wings are running using systemctl status wings and that your Wings ports (by default 8080/2022) are open in your firewall or router. This website can check your ports https://dnschecker.org/port-scanner.php
Browser console errors can also provide additional debugging information. More troubleshooting steps can be found at https://pterodactyl.io/panel/1.0/troubleshooting.html#cannot-connect-to-server-errors
Should the panel and wings be located on the same network, you might experience NAT reflection issues. In that case, type .nat for more information.
autumn crow
floral heartBOT
Suppose you are having trouble connecting to a Panel or Node on the same network as your device, or Panel and Wings can't reach each other on the same network. In that case, you may have to edit your /etc/hosts file to point the domain to the local IP, as some routers don't handle NAT Loopback correctly, if at all. On Windows, this file is at C:\Windows\System32\Drivers\etc\hosts
192.168.1.24 panel.mydomain.com node1.mydomain.com
192.168.1.25 node2.mydomain.com
Precisely when I use my public IP it no longer works but when I am on my local IP I have no problem
Yes, I am doing it well
autumn crow
I found my problem but I don't see how to solve it if someone has an idea in pm
Since I'm doing port forwarding, I use port 80 for HTML output but the web interface tries to make requests to a public IP address when I'm on my public IP
hearty pebble
Lmaooo so wrong
You use the local IP of a server as an allocation.
You connect to the server with the public IP.
Don't spread obviously wrong info..
hearty pebble
The problem: you used a local IP as FQDN for ur node, use ur public ip, forward ports, re-do ur config.yml file, restart wings and check again.
floral heartBOT
Simple! 😘
systemctl restart wings
drowsy spruce
If this still doesn’t work, as in works when it’s routed to local IP FQDN, but doesn’t on public, and you need to acces it from outside your network, do
floral heartBOT
Suppose you are having trouble connecting to a Panel or Node on the same network as your device, or Panel and Wings can't reach each other on the same network. In that case, you may have to edit your /etc/hosts file to point the domain to the local IP, as some routers don't handle NAT Loopback correctly, if at all. On Windows, this file is at C:\Windows\System32\Drivers\etc\hosts
192.168.1.24 panel.mydomain.com node1.mydomain.com
192.168.1.25 node2.mydomain.com
And use the public IP
hearty pebble
Already fixed @drowsy spruce