#Cloudflare compatible with pterodactyl?

18 messages · Page 1 of 1 (latest)

upper prairie
#

Hello, is cloudflare compatible with ptreodactyl? Because my server uses a proxy to cloudflare. I have setup my A record to the panel in cloudflare and changed proxy to DNS only. But seems it can't connect still? When I do "curl -k https://panel.arclight-hosting.com:8443/ping" I should get pong but it says {"error":"The required authorization heads were not present in the request."}

upper prairie
#

Cloudflare compatible with pterodactyl?

severe sandBOT
#

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.

upper prairie
#

okey but this isn't a proxy anymore but a DNS Only like I said. Anyone has idea's or has setup cloudflare earlier with pterodactyl?

quasi socket
#

You can use whatever DNS you want. It’s completely separate from pterodactyl.

#

The response you’re getting is the one you should be getting. so Nothing to worry about

upper prairie
#

so why won't it connect than? I do not understand. I have the SSL setup "fullchain.pem" + "privkey.pem". DNS stands on DNS Only. Wings get connected. config.yml is okey: "debug: false
app_name: Pterodactyl
uuid: c0f1b389-b13b-4635-bc45-6b15b0227936
token_id: 8At7qNjd3ztR8lGY
token: kymFol69CrqaEaoKOKsZXwLgh39F8k8Ask1JgXx6Xv2kALr3og13PNcGr4y6XuoP
api:
host: 0.0.0.0
port: 8443
ssl:
enabled: true
cert: /etc/letsencrypt/live/panel.arclight-hosting.com/fullchain.pem
key: /etc/letsencrypt/live/panel.arclight-hosting.com/privkey.pem" my ports are okey and running perfectly. I'm missing something.

severe sandBOT
#

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.

#

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.

fast compass
#

You haven't even shown that there is an issue yet. All we've seen is wings running perfectly.

upper prairie
#

I might have found the issue. Checking it right now but I think I just had the wrong token.

upper prairie
#

No it's not the issue. It says: "Failed to load resource: net::ERR_NAME_NOT_RESOLVED"

severe sandBOT
#

The domain you are trying to reach does not have valid DNS records or the DNS cache of your machine has not been updated yet. You can use https://dnschecker.org/ to verify the DNS records of a domain.

upper prairie
#

but I have changed the DNS. Or is this wrong?

#

A panel 135.181.151.26 DNS only Auto

#

Waaauuwww

#

Issue was typography related I used "-" but it's "-"

#

seems the same but is completly different lol