#WebSocket problem

11 messages · Page 1 of 1 (latest)

dense maple
#

Hey, everybody, I have a problem.

I have installed pterodactyl panel on my home lab and pterodactyl panel on my VPS. In order to connect these two servers I am using netbird. When I try to navigate to the server page I get the following errors:

WebSocket connection to 'ws://100.104.129.85:8080/api/servers/b1d608ae-637a-442e-a4b1-27df01156c59/ws' failed: WebSocket is closed before the connection is established.

WebSocket connection to 'ws://100.104.129.85:8080/api/servers/b1d608ae-637a-442e-a4b1-27df01156c59/ws' failed:
WebSocket is already in CLOSING or CLOSED state.

image.png
cyan aurora
#

@dense maple get logs

rigid roverBOT
#

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

cyan aurora
#

And

rigid roverBOT
#

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

cerulean ember
#

can someone tag me when fix is found i have same problem

faint escarp
cerulean ember
#

i know i made one also yesterday

rigid roverBOT
#

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.

wet turret
cerulean ember