Panel cannot connect to node

[vapid siren]

Hi everyone.

I am trying to get my Pterodactyl game server up and running, and I am struggling on getting the panel to connect to the node.

I am following this tutorial by Techo Tim: https://www.youtube.com/watch?v=_ypAmCcIlBE&t=773s&ab_channel=TechnoTim

However, my environment is kind of different.

I am running Proxmox and I have Traefik LXC, so all my configs have to specified in my /etc/traefik/conf.d directory at the Proxmox host, and I have an Alpine Linux VM where I am trying to set up Pterodactyl Panel and Node containers there.

I configured Traefik to detect my subdomain for the panel, and I added the DNS entry, and I was able to get to the panel at gameserver.mydomain.com

I also did the same with the node at gameserver-node-01.mydomain.com

However there is some confusion in terms of the ports. According to the video tutorial, he said that I have to use port 443 as my daemon port. Well when I did that, and then pasted the configuration into the VM's /etc/pterodactyl/config.yml, and then respin the wings container, panel says that it still couldn't connect to the node. An important point to note is that because both containers want to have port 443, it will create collisions in the VM itself, so I made the wings container have this mapping: 4443 -> 443.

I changed it to use port 8080, and changed the config for Traefik and I'm not getting any luck.

I wanted to ask, how do I go about solving this problem?

[quaint echo]

Videos like this generally arent recommend, follow the official docs

[brisk sage]

The documentation you are looking for can be found at https://pterodactyl.io/.

[vapid siren]

Oh as an update, I got pretty close to solving my issue.

Right now I am getting a CORS error when panel tries to connect to node.

[frigid python]

Provide the full error and we might be able to help

[vapid siren]

I resolved the CORS issue by updating Traefik config, and now I am getting these errors.

YESSSS!!!

I got it to work!

Alright. I'll tell you what happened.

The issue was the confusion with where the request was going and the ports involved.

Initially, the panel was trying to send a request to my address with port 8080, but traefik was also trying to forward traffic from 443 of the subdomain to the port. Because of that nothing was getting served.

Then I fixed the issue, by having the panel use port 443. That way traefik can then direct back to the same VM.

Then I got the CORS issue. I added a middleware to resolve that in Traefik.

Then I got the 404 errors here. This confused me, but then I realized that Traefik terminated the SSL, and I am directing it back to the same VM but on port 80, a port that the panel was listening to.

So the panel ended up going back to itself.

I then realized that I have to tell Traefik to direct to request to the VM at port 4443. That way, the node can get that and map it to 443 internally.

This solved my problem!

Thanks everyone! 😄