#Can't connect to node (sometimes)

18 messages · Page 1 of 1 (latest)

near axle
#

Hey! I cannot create a new server on my node. On the /admin/nodes page, I have a green heart indicating it connected successfully, but when I click on the node, there are three spinning loading indicators and the system-information request times out.

#

Ports 8080, and 2022 are both forwarded.

runic elmBOT
#

I have found the following for: https://media.discordapp.net/attachments/1110020743565168751/1110021326388875344/image.png
@near axle It looks like you are having issues with connecting to Wings.

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.

near axle
#

systemctl status wings does not return any errorr.

runic elmBOT
#

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
near axle
#

(panel and server running on same machine, for now)

#

I also get the error: ERR_CERT_COMMON_NAME_INVALID

runic elmBOT
near axle
#

Is this due to me running it on the same machien

#

panel and node on same machine

near axle
runic elmBOT
#

I have found the following for: https://ptero.co/jevylejozo
@near axle Your Panel has not been configured to listen on port 443 and use an HTTPS connection, or it's currently unreachable.

If your Panel is running and reachable on HTTPS, try restarting the failed-count systemctl reset-failed wings && systemctl restart wings. Otherwise, look into your web server status and its configuration to ensure SSL configuration is being used.

near axle
runic elmBOT
#

I have found the following for: https://ptero.co/ekalixoteb
@near axle Your Panel has not been configured to listen on port 443 and use an HTTPS connection, or it's currently unreachable.

If your Panel is running and reachable on HTTPS, try restarting the failed-count systemctl reset-failed wings && systemctl restart wings. Otherwise, look into your web server status and its configuration to ensure SSL configuration is being used.

near axle
#

hmm

#

panel is reachable on https

#

and restarting failed-count didn't help