#Multiple Qs regarding Cloudflare and Nodes

17 messages · Page 1 of 1 (latest)

pseudo kestrel
#

I was previously using CubeCoders but I want to give Ptero a try, potentially switching over because of financial prospects. I wanted to spin up an environment and I was able to get the main agent running in one VM, all running nicely. When I made a location and wanted to make my first node however, I stumbled across multiple hurdles. I have the wings node in a separate VM and have it all installed, but I dont get it to connect using port 8080. I saw in the Discord that someone mentioned that using 8443 is mandatory when using Cloudflare to expose services. But in both instances, because I'm using SSL, I get 'error:0A00010B:SSL routines::wrong version number ' errors when trying to curl into the port. Am I missing something? I have Nginx Proxy Manager running on my WAN interface and I even tried adding an entry for https://WingsIP:8443, even with 4443 or 16443, all giving out the same error. Also - Do the wings nodes also have to be exposed outside, or only internally?

#

Also to note, I followed the instructions in the page and I am using the FQDN

#

First is the curl try which reflects in the logs, second is the config in cloudflare currently

tepid dawnBOT
#

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.

pseudo kestrel
#

Oh no worries, I got it fixed and found the scope of the problem. Funnily enough, it was becasue of the misisng certs.

#

But I appreciate the comment

#

Only question left is,

#

Do the wings haev to be exposed to the outside?

snow charm
pseudo kestrel
#

@snow charm So keeping the IP of the wings internal (10.x.y.z) and not exposed to the outside is okay? Only the panel is publicly accessible

#

At the moment

snow charm
#

No

#

As I said, anyone accessing the panel MUST be able to talk to wings

#

They can't do that when wings is configured for a local IP address, or otherwise not exposed to the internet

pseudo kestrel
#

Ah okay! So basically in other words - keep both the panel and the wings (in my case 3, 1 per cluster node I own) exposed to the outside

#

I just got it working with one panel and one wing with some tinkering - the problem was definitely certificate based