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

43 messages · Page 1 of 1 (latest)

worldly sequoia
#

What is this error?

exotic sluiceBOT
#

I have found the following for: https://media.discordapp.net/attachments/1116655136341757972/1116655136509534309/image.png
@worldly sequoia; 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.

steel owl
#

I'll be surprised your ip will be 0.0.0.0

worldly sequoia
steel owl
#

Or dedicated server

worldly sequoia
steel owl
#

which server do you use?

worldly sequoia
#

I have a server at home and build with Proxmox on it.

steel owl
#

what is the operating system?

#

if you don't have an ip you can't start wings

worldly sequoia
steel owl
#

pterodactyl works only under its operating systems

worldly sequoia
#

CT image file is Ubuntu

steel owl
#

but do you have ip

worldly sequoia
#

Is the IP a LAN IP or a WAN IP?

steel owl
#

the ipv4 of your virtual machine

#

you have to enter it in node ports

worldly sequoia
steel owl
#

Yes

worldly sequoia
#

i see

#

What is IP Alias and Ports?

#

As for ports, I see that the port numbers are 0~65535, but I don't know which number to put in.

steel owl
#

alias is not required and as ports I advise you to enter 30100-30200

#

put well pull it in both ports

#

because its indicates to create 100 allocations so that it is faster

worldly sequoia
#

i see

hushed sigil
#

If you're using a Proxmox LXC container for wings, make sure to enable nesting btw.

#

Your container will have an IP. Proxmox uses DHCP by default unless you gave it one manually.

hushed sigil
#

It's not related to the issue this thread is about, but it is something you'll need to enable if you want the servers to function normally when you resolve your node connection issue.

worldly sequoia
hushed sigil
#

It's a Proxmox thing, not a panel thing. You just go to the container, go to options, and check nesting.

hushed sigil
#

DW about that then. As for your wings connectivity issue, you'll need to get the error message from your browser. F12 -> Console

worldly sequoia
#

Is this a problematic condition?

hushed sigil
#

No, that just means without a VPN or tunnel your panel can only be accessed locally, and there is no encryption.

Go to Admin -> Nodes and then fetch the error message from your browser's console.

#

Fetch wings logs as well:

exotic sluiceBOT
#

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

hushed sigil
#

Remember to stop the Wings Service before running diagnostics: sudo systemctl stop wings