#How to fix...

51 messages · Page 1 of 1 (latest)

agile island
#

Error Event [0e854ad1-04e4-46a5-a4f4-e6ae5941f5eb]: unable to sync server data from Panel instance: http: request creation failed: Get "https://examplepanel.com/api/remote/servers/319e385b-ee8e-4854-bac8-ec5266540961": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Im running wing and panel in cloudflare tunnel, and both in the same vps. using port 443 for wings, and then in the tunnel, its forwarded to 8080 by cloudflare.

true patioBOT
#

@agile island; It looks like the Panel or Wings is responding too slowly, causing the request to timeout. Usually, this indicates some sort of a network issue.

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
agile island
#

cloudflare tunnel is being used

#

@true patio

delicate flame
#

The bot is not AI xD

agile island
#

Yea

#

thats why i said u to help : )

delicate flame
#

I believe that things related to Cloudflare the bot has no answers.
But that's a configuration problem on your end.

#

I have no clue about cf

agile island
#

btw 443 is forwarded to cf for wings, and wings forwards it to 8080, the default

delicate flame
agile island
#

alr

lost tangle
#

using cloudflare has nothing to do with a nat loopback issue. Cloudflare doesnt magically solve a nat reflection issue. and why are you using port 443 for wings. its already used by nginx. So do what the bot says.

agile island
#

but it again comes.

#

this is the same server that got that error b4

#

can u understand me?

#

its kinda like random

#

if the wings want to communicate with panel, or vice versa

delicate flame
#

just restart wings

true patioBOT
#

Simple! 😘

systemctl restart wings
lost tangle
#

you need to choose a port that cloudflare allows https traffic through which is port 443, 8443 and others. If you run wings using port 8080 and then change it to 443 in the panel. it breaks entirely as soon as wings restarts bcs it cant use port 443 since its already in use by nginx.

true patioBOT
#

Simple! 😘

systemctl restart wings
agile island
#

Hmm

lost tangle
#

so actual read on what your doing instead of blindly following a tutorial thats outdated and wrong.

#

only supported way is the docs.

true patioBOT
agile island
#

Alr

agile island
# lost tangle you need to choose a port that cloudflare allows https traffic through which is ...

https://youtu.be/a3ZRc9-98qw?si=CWQbJVIexYwv0Dt3

"This video explains exactly what I'm trying to explain"

In this video we'll install the Pterodactyl Panel and Wings behind a Cloudflare tunnel. With this setup you will not need to open any ports for the Panel or Wings. You'll only need to open ports for the game servers you run.

TIMESTAMPS
00:00 Intro and Prerequisites
1:00 Installing the Panel
3:50 Nginx Web Server Configuration
5:56 Installing Wi...

▶ Play video
#

Bro said this

lost tangle
#

yeah and that video is outdated and wrong. especially in the wings setup. Like i said already following videos isnt recommended as most are wrong and outdated.

lost tangle
#

You do you. I'm not gonna repeat myself. The problem lies that you followed a video that's outdated and wrong. Redo it using the docs. Then, if you run into any problems, you can ask for help in the respective channels.

wild yew
#

To enable Cloudflare proxy, you must change the Wings port to one of the Cloudflare HTTPS ports with caching enabled (more info here (opens new window)), such as 8443, because Cloudflare only supports HTTP on port 8080. Select your Node in the Admin Panel, and on the settings tab, change the port. Make sure that you set "Not Behind Proxy" when using Full SSL settings in Cloudflare. Then on Cloudflare dashboard, your FQDN must have an orange cloud enabled beside it. https://pterodactyl.io/wings/1.0/configuration.html#enabling-cloudflare-proxy As Maarten stated 443 is already in use of your webserver.

agile island
#

Bruh

lost tangle
#

its still getting proxied through cloudflare. tunnel or not

agile island
#

i changed all the related port for cloudflare, vps node config, and ptero node daemon port to 8443, and it fixed it. thanks

#

but no

true patioBOT
#

@agile island; It looks like the Panel or Wings is responding too slowly, causing the request to timeout. Usually, this indicates some sort of a network issue.

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.

agile island
#

still here

agile island