#Infinite loading of servers panel - Wings

46 messages · Page 1 of 1 (latest)

heavy larkBOT
#

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
upbeat oracle
#

Nah, its not working

proven oasis
#

Well you don't want to mess with the hosts file.

#

What did the troubleshooting tell you ?

upbeat oracle
#

Nothing, it's just saying that he does have problem to connect to my server. The problem is only the console, I can access to it, but not interact with it

proven oasis
#

Ok.. so it didn't say nothing

#

Lets start with, what did the port checker say ?

upbeat oracle
#

its open

#

well

#

lemme verify

#

What ports?

#

Well

#

Which ones

proven oasis
#

You were told what ones..

upbeat oracle
proven oasis
#

Great.

#

So what did the browser console say ?

upbeat oracle
#

This

heavy larkBOT
#

I have found the following for: https://media.discordapp.net/attachments/1448785747879399568/1448797220534222868/image.png?ex=693c910e&is=693b3f8e&hm=5458ed7a74af07c34797ff27174da80ed6c2a2c786462c6bf7323a9edab5571d&
@upbeat oracle; 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.

proven oasis
#

No. The browser console

#

This was part of the troubleshooting steps you were provided, so clearly you did not actually complete them.

upbeat oracle
upbeat oracle
proven oasis
#

You have used http://192.168.2.91 as your panels address in your config files.
You need to use the proper address, the one you will be using when accessing it from everywhere.

#

Correct the APP_URL in your .env file and the remote: field in your wings config.yml

heavy larkBOT
#

The env file can be found at /var/www/pterodactyl/.env. Files starting with a . in Linux are hidden so it may not show up in file browsers by default. You can open it directly with nano /var/www/pterodactyl/.env

proven oasis
#

and then restart wings

heavy larkBOT
#

Simple! 😘

systemctl restart wings
upbeat oracle
#

Wow, lemme try to understand

#

First thing, how do I change the panel address?

proven oasis
#

You need to edit the config files as I just said

upbeat oracle
#

config.yml, okay, lemme go there

proven oasis
#

and the .env file

heavy larkBOT
#

The env file can be found at /var/www/pterodactyl/.env. Files starting with a . in Linux are hidden so it may not show up in file browsers by default. You can open it directly with nano /var/www/pterodactyl/.env

upbeat oracle
#

Okay, the remote was incorrect and binded to my local one, 192.168.2.91.

proven oasis
#

Remove the trailing /

upbeat oracle
#

Oh

#

At the app url and the remote ?

proven oasis
#

Yes

upbeat oracle
#

It worked, now !

#

To resume, does the problem was that I had different IP's binded ?

proven oasis
#

Your panel address (the APP_URL and the remote:) MUST match the address you actually put in your address bar to access the panel.
Mismatch causes the error