#Red heart over Grey cloud

46 messages · Page 1 of 1 (latest)

supple pagodaBOT
#

Pterodactyl has features to enable use of proxies, however we cannot provide support for proxies as it adds great complexity to the application set up. Troubleshooting complex network setups involving tunnels and proxies is extremely difficult to do without access to that network. Supporting complex network issues is outside the scope of this support.

neat galleon
#

Cool, it doesn't work without proxies enabled, so what are my options?

supple pagodaBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

neat galleon
supple pagodaBOT
neat galleon
#

They are made, they just don't work.

supple pagodaBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

neat galleon
#

The certs are made they just don't seem to work

neat galleon
restive mountain
#

as you said in wings help. Your also proxying through nginx. So what the said in the beginning still applies.

neat galleon
restive mountain
#

cloudflare only allows http and https in their free plan. So either find a alternative or pay for the expensive cloudflare spectrum if you want to proxy both TCP and UDP traffic

#

hence the reason why UDP traffic isnt getting through

neat galleon
restive mountain
#

check if wings is running using systemctl status wings. If it is something is, then something is blocking it so check firewalls and port forwarding if it applies to your setup

restive mountain
neat galleon
#

8443 shows as open

#

The problem is that it doesn't want to communicate with the panel, the container does not run and the heart don't turn green

supple pagodaBOT
#

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.

neat galleon
supple pagodaBOT
#

I have found the following for: https://ptero.co/jizejesoxe
@neat galleon; You chose to redact the logs. There is nothing for us to read.

neat galleon
merry path
neat galleon
#

SSL

#

And I tried both 8080, 443, 8443, nothing @merry path

merry path
#

And what does your browser console tell you?
You need to use the same port wings is using. SSL or not, it doesn't matter

neat galleon
#

I keep remaking the diagonistics and you read the first line which was an older test

#

It will 100% run if I activate the orange cloud, which I don't understand why it won't work on the grey cloud

merry path
#

Again, what does your browser console tell you?

supple pagodaBOT
#

I have found the following for: https://ptero.co/wihuhufija
At your service, @neat galleon!

The IP address you have assigned to your server is not actually available for use on your machine. Node allocation creation is explained in the Wings install documentation: https://pterodactyl.io/wings/1.0/installing.html#node-allocations

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. When behind NAT you will allocate the internal IP and connect using the public IP.

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

merry path
#

I don't care about your wings diagnostics

neat galleon
#

The bot read the first line again, I already set to 0.0.0.0

neat galleon
merry path
#

Your BROWSER console

neat galleon
neat galleon
merry path
#

On the nodes page. Where you get the red heart

neat galleon
#

Nothing shows up

supple pagodaBOT
#

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
neat galleon
supple pagodaBOT
#

@neat galleon You don't have HTTPS enabled or are missing the SSL certificate that would be generated by following our guide: https://pterodactyl.io/tutorials/creating_ssl_certificates.html

When using Cloudflare proxy for your Wings FQDN, the Node/Wings Port should be set to 8443, which is a HTTPS Port on Cloudflare. The default Wings port 8080 is HTTP only on Cloudflare and, as such, will cause SSL protocol errors. Make sure to have Node settings set to "not behind proxy" when using full SSL settings.

neat galleon