#Help with connection wings
29 messages · Page 1 of 1 (latest)
If you're still experiencing this issue, run systemctl status wings on the machine running wings.
root@b2-15-de1:~# systemctl status wings
● wings.service - Pterodactyl Wings Daemon
Loaded: loaded (/etc/systemd/system/wings.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-12-11 20:43:14 UTC; 17h ago
Main PID: 55919 (wings)
Tasks: 10 (limit: 17533)
Memory: 9.8M
CGroup: /system.slice/wings.service
└─55919 /usr/local/bin/wings
Dec 12 06:49:42 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:49:44 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:49:45 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:49:46 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:22 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:23 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:23 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:23 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:24 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir>
Dec 12 06:50:24 b2-15-de1 systemd[1]: /etc/systemd/system/wings.service:11: PIDFile= references a path below legacy dir
WORK
I have found the following for: https://pteropaste.com/7matkj
@torn sun; You appear to have mismatched HTTP/HTTPS protocols. Both Panel and Wings must have a SSL certificate and use HTTPS to communicate with each other if either one of them is using HTTPS.
Should you be proxying your Wings through Cloudflare, please read this: https://pterodactyl.io/wings/1.0/configuration.html#enabling-cloudflare-proxy
Your wings must be reachable by your users web browsers by the "Fully Qualified Domain Name". So you can't use 127.0.0.1/localhost
You just point your (sub)domain at the servers IP address
@torn sun You don't have HTTPS enabled or are missing the SSL certificate that would be generated by following our guide: https://pterodactyl.io/tutorials/creating_ssl_certificates.html
When using Cloudflare proxy for your Wings FQDN, the Node/Wings Port should be set to 8443, which is a HTTPS Port on Cloudflare. The default Wings port 8080 is HTTP only on Cloudflare and, as such, will cause SSL protocol errors. Make sure to have Node settings set to "not behind proxy" when using full SSL settings.
i have certifikate
tail: cannot open '/var/www/pterodactyl/storage/logs/laravel-2022-12-12.log' for reading: No such file or directory
if i try
to
log
GET https://node.host.pl:8080/api/system net::ERR_CONNECTION_REFUSED
@torn sun 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
● wings.service - Pterodactyl Wings Daemon
Loaded: loaded (/etc/systemd/system/wings.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-12-12 15:00:58 UTC; 1s ago
Process: 102701 ExecStart=/usr/local/bin/wings (code=exited, status=1/FAILURE)
Main PID: 102701 (code=exited, status=1/FAILURE)
I have found the following for: https://ptero.co/uporumelir
@torn sun; 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
GET https://node.vikshost.pl:8080/api/system net::ERR_CONNECTION_REFUSED
@torn sun 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
root@b2-15-de1:~# systemctl status wings
● wings.service - Pterodactyl Wings Daemon
Loaded: loaded (/etc/systemd/system/wings.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-12-12 15:46:22 UTC; 2s ago
Process: 105770 ExecStart=/usr/local/bin/wings (code=exited, status=1/FAILURE)
Main PID: 105770 (code=exited, status=1/FAILURE)