#We're having some trouble connecting to your server, please wait...

8 messages · Page 1 of 1 (latest)

potent anvil
#

Getting this error in my MGMT panels
We're having some trouble connecting to your server, please wait...

I have already restarted wings itself and the enitre wings VM and it did not help.

steep condorBOT
#

@potent anvil; 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.

potent anvil
#

From wings vm
To Action From

22 ALLOW Anywhere
8080 ALLOW Anywhere
2022 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
8080 (v6) ALLOW Anywhere (v6)
2022 (v6) ALLOW Anywhere (v6)

From Panels vm
8080 ALLOW Anywhere 2022 ALLOW Anywhere

steep condorBOT
#

We need some logs from you in order to help debug this issue.
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.

potent anvil
steep condorBOT
#

I have found the following for: https://ptero.co/nevibokira
At your service, @potent anvil!

The IP address you have assigned to your server is not actually available for use on your machine, or something is already running on that port. Use ss -plnt | grep :<port> (replacing <port> with your own) to find what processes might be using it.

If you don't find any service using the port, then refer to the instructions below.

Execute the command hostname -I | awk '{print $1}' and change your Node allocations to use this IP. Yes, it can be your internal/local IP when you're behind NAT. You still have to use it as that is your network interface IP.

If you have added multiple public IPs to your network interface, then you can view all of them using the command ip a | grep "inet "

potent anvil
#

From wing VM

Running hostname -I | awk '{print $1}'
192.168.7.177

Running ip a | grep "inet "
inet 127.0.0.1/8 scope host lo
inet 192.168.7.177/24 metric 100 brd 192.168.7.255 scope global dynamic ens33
inet 172.18.0.1/16 brd 172.18.255.255 scope global pterodactyl0
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

From Panels VM

Running hostname -I | awk '{print $1}'
192.168.7.249

Running Running ip a | grep "inet "

inet 127.0.0.1/8 scope host lo
inet 192.168.7.249/24 metric 100 brd 192.168.7.255 scope global dynamic ens33
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
#

Any tips?