ebon hornet
Hi! I have a a Pterodactyl Panel self-hosted on a debian 13 machine I run at home. I have spent several hours trying to troubleshoot but no matter what I cannot successfully connect even from inside the same network. Any and all help would be greatly appreciated!
solemn steppeBOT
I have found the following for: https://media.discordapp.net/attachments/1441262160226418739/1441262161216147557/image.png?ex=6921277c&is=691fd5fc&hm=5b4ea4088c6c1f6c0edf645db62e87956fa5cf6f3187090d316cbd346f7b2ccb&
@ebon hornet; It looks like your browser is unable to reach the 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.
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
unkempt hemlock
check logs and browser console for any errors
solemn steppeBOT
You'll need to grab the error logs from the Panel. The following command uploads the last 150 lines of this day's log to our pastebin and provides a link you can share.
tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
You'll need to grab error logs for Wings and share the link with us. The following command will help you collect the required information for debugging: sudo wings diagnostics
ebon hornet
check logs and browser console for any errors
I checked it out many times never saw any errors or warns show in the console