#homelab panel and VPS wings connection issue

1 messages · Page 1 of 1 (latest)

hardy mason
#

Hello, I am trying to connect the pterodactyl panel (docker compose) of my homelab to wings (docker compose) on my VPS via tailscale. After several days of various errors, I have now reached the point where I have managed to “connect” them, but the problem is that I have the compose APP_URL pointing to a DNS that resolves my homelab (pterodactyl.mydomain.xyz) and then a second domain (panel.mydomain.xyz) pointing to the Tailscale IP of my VPS, but selecting the DNS pterodactyl.mydomain.xyz in APP_URL sends the health request to an IP that actually belongs to my homelab and not to the VPS, and I can't even change it because otherwise I wouldn't even be able to log in. Is there a way to set it up so that it sends requests to the other DNS?

elder fableBOT
#

I have found the following for: https://media.discordapp.net/attachments/1464991685074223336/1465448863149330604/image.png?ex=6979251b&is=6977d39b&hm=51e37fbf722f449e20a8366316436b619f74e77bc06e6a7423c9edd97ad4ca42&
@molten maple; It looks like your browser is unable to reach the Wings.

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.