The panel cannot connect to the docker container anymore after an update. It says We're having some trouble connecting to your server, please wait... The panel has still connection to the wings as I can still see the resource usage of the servers but tryign to get into the console doesn't work. Restarting the system doesn't work either. Firewall is configured correctly;
#Panel cannot connect to the docker container
10 messages · Page 1 of 1 (latest)
@thick ledge; It looks like your browser is unable to reach the 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.
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
FATAL: [Nov 24 22:52:12.541] failed to configure HTTP server error=listen tcp 0.0.0.0:8080: bind: address already in use
Stacktrace:
listen tcp 0.0.0.0:8080: bind: address already in use
github.com/pterodactyl/wings/cmd.rootCmdRun
github.com/pterodactyl/wings/cmd/root.go:375
github.com/spf13/cobra.(*Command).execute
github.com/spf13/[email protected]/command.go:987
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/[email protected]/command.go:1115
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/[email protected]/command.go:1039
github.com/pterodactyl/wings/cmd.Execute
github.com/pterodactyl/wings/cmd/root.go:71
main.main
github.com/pterodactyl/wings/wings.go:17
runtime.main
runtime/proc.go:267
runtime.goexit
runtime/asm_amd64.s:1650
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.
still same error
6WebSocket connection to 'ws:<URL>/api/servers/36be8edf-8622-4be8-8737-6c70f8f30828/ws' failed: WebSocket is closed before the connection is established.```
😢
@thick ledge 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.