connection refused error | Pterodactyl® | Page 1

opal echoBOT Feb 4, 2025, 2:01 AM

#

@deep sandal 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.

deep sandal Feb 4, 2025, 2:02 AM

#

Feb 04 01:54:00 panel systemd[1]: wings.service: Scheduled restart job, restart counter is at 30.
Feb 04 01:54:00 panel systemd[1]: Stopped Pterodactyl Wings Daemon.
Feb 04 01:54:00 panel systemd[1]: wings.service: Start request repeated too quickly.
Feb 04 01:54:00 panel systemd[1]: wings.service: Failed with result 'exit-code'.
Feb 04 01:54:00 panel systemd[1]: Failed to start Pterodactyl Wings Daemon.
root@panel:/home/max#

opal echoBOT Feb 4, 2025, 2:02 AM

#

@deep sandal You'll need to grab error logs from Wings. The following command allows to easily collect the relevant data and share the link with us: sudo wings diagnostics

deep sandal Feb 4, 2025, 2:03 AM

#

https://ptero.co/ipebujuqij

opal echoBOT Feb 4, 2025, 2:03 AM

#

I have found the following for: https://ptero.co/ipebujuqij
@deep sandal; Wings must have a certificate to use when SSL is enabled. Follow this guide to learn how to generate SSL certificates: https://pterodactyl.io/tutorials/creating_ssl_certificates.html

#connection refused error