#Node is not recognized.
19 messages · Page 1 of 1 (latest)
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.
systemctl status wings
● wings.service - Pterodactyl Wings Daemon
Loaded: loaded (/etc/systemd/system/wings.service; enabled; vendor preset:>
Active: active (running) since Tue 2024-08-06 17:52:26 UTC; 17min ago
Main PID: 1386 (wings)
Tasks: 22 (limit: 76922)
Memory: 327.0M
CPU: 11.920s
CGroup: /system.slice/wings.service
└─1386 /usr/local/bin/wings
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
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://node.mystic-celduin.de:8080/api/system. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).
I can access the servers but not the files.
I have found the following for: https://media.discordapp.net/attachments/1270442639585443941/1270448930290925699/image.png?ex=66b3bd44&is=66b26bc4&hm=9a30ec289aea7ffd98200c2b2b5316b2b91bbb92cada8c77532f014d307143ff&
@fresh cliff 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.
wings.service - Pterodactyl Wings Daemon
Loaded: loaded (/etc/systemd/system/wings.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-08-06 18:28:10 UTC; 3min 33s ago
Main PID: 1380 (wings)
Tasks: 24 (limit: 76922)
Memory: 325.9M
CPU: 5.008s
CGroup: /system.slice/wings.service
└─1380 /usr/local/bin/wings
Aug 06 18:31:06 Ubuntu-2204-jammy-amd64-base wings[1380]: 2024/08/06 18:31:06 http: TLS handshake error from xxxxxx:43248: local error: tls: bad record MAC
You need to generate or renew a new valid certificate matching your domain. View our guide at https://pterodactyl.io/tutorials/creating_ssl_certificates.html
Howdy @marble ivy! It looks like your SSL certificate has probably expired which is causing you some issues. Please double check that it is up-to-date and renew it if needed by following our guide https://pterodactyl.io/tutorials/creating_ssl_certificates.html
Additionally, not every service is able to automatically apply an updated certificate so you may need to restart Wings, NGINX, or Apache so that they will begin using the updated certificate.
This was renewed tonight at 1am.
Wings is still presenting an expired certificate
Did you perhaps forget to restart wings afterwards ?
Simple! 😘
systemctl restart wings
There is no record of you recently renewing this certificate at all. Are you sure you renewed the correct one ?
😄
Restarting the root should have done the same thing...
well, it works again...
The Certbot should renew all cerficates because they expired today at 01 o'clock.
But apparently he didn't do that but everyone else did 😄
Better to actually check next time instead of assuming certbot did what you expected it to