When trying to connect Wings to my pterodactyl panel, everything goes fine (even the green heart is lit), but the server is not created and when entering this node, the kernels and other system information are endlessly loaded
#Pls help this error
desert dew
grim oracleBOT
I have found the following for: https://media.discordapp.net/attachments/1364138483991445524/1364138485132427274/image.png?ex=68089477&is=680742f7&hm=2d5ae352eaa1c4f20de3a076c8b1bababf7721b0bb03c82edcc143ce271b9bfd&
@desert dew 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.
grim oracleBOT
Hello 👋, and welcome to the Pterodactyl Discord @desert dew! We're excited to see you here, but we'll likely need a bit more information from you in order to provide a good experience in these support channels.
Always share any errors or logs in a text format or using paste sites for me to assist you. Please make sure you've collected — and provide — any associated error logs relating to the service with which you're seeking help. The commands below should help you out, and once you've provided the logs I should be able to better assist you.
Panel: tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
Wings: sudo wings diagnostics
Please see .plogs and .wlogs respectively for more information.
desert dew
grim oracleBOT
I have found the following for: https://ptero.co/uyukirozoy
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.
desert dew
grim oracleBOT
I have found the following for: https://ptero.co/icimegegez
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.
desert dew
not worked
grim oracleBOT
I have found the following for: https://ptero.co/sopuxibodu
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.
desert dew
I have found the following for: <https://ptero.co/sopuxibodu>
You already have a...
stuped bot
fossil rover
stuped bot
Not really
Thats the only error of concern in that loga
SFTP errors aren't relevant to reaching wings via http
hardy oar
Spamming "not worked" and dumping irrelevant logs into chat isn't going to get you anywhere.
Your panel can't reach wings. So look at your panel logs