#Wings won't start after IP change.

5 messages · Page 1 of 1 (latest)

orchid basin
#

Hey all.. So I got a new router and tried setting up my home server (Pterodactyl) so it works with my new router. I mostly fixed everything except wings. For some reason, it won't start. I tried rebooting, and updating the config, but no luck. When I type sudo wings --debug I get the attached error. I would appreciate any help.

rustic flintBOT
#

I have found the following for: https://media.discordapp.net/attachments/1067296425567850516/1067296425731444777/image.png
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

orchid basin
#

That fixed the used port issue! However, my wings still isn't working. When I look at my console it's fine.. but wings is still down.

rustic flintBOT
#

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.