[HELP] Unable to Access Exposed Resources via Pangolin (Getting 404)

[KamilKleina]

Description

I could use some help in exposing resources from another server using Pangolin.

My Setup

I have multiple machines on my local network running various services that I want to expose using Pangolin.

• Installed LXC on my Proxmox server, which has access to all of these services.
• Inside the LXC, I installed Docker and set up Newt.
• The Newt instance is online and visible on my Pangolin server.
• Pangolin is hosted on a VPS outside my local network.

What I Did

• I attempted to expose an HTTPS resource.
• I specified a URL that is accessible from within the LXC.
• However, when I visit the URL provided by Pangolin, I only see a 404 error.

My Network Setup (Simplified)

1. Local Network Setup:

   • Router with local DNS that resolves *.machine-01.home.domain.com to the IP of machine-01.
   • machine-01 runs Docker containers (e.g., Traefik-managed services):
     • Example: hello-world.machine-01.home.domain.com

2. Proxmox Setup:

   • Proxmox (machine-02) has an LXC that can access hello-world.machine-01.home.domain.com without issues.
   • Newt is running in Docker inside the LXC on Proxmox.

3. Pangolin Setup:

   • Pangolin is running on VPS (pangolin.remote-01.not-home.domain.com).

The Issue

I added the resource via Pangolin, expecting to access:

https://hello-world.remote-01.not-home.domain.com

However, I only get a 404 error.

Debugging Attempts

• Checked Traefik logs and Pangolin logs but did not find anything helpful.

Question

How can I properly debug this issue?
What could I be doing wrong in my setup?

Any help would be greatly appreciated!

[oschwartz10612]

This is typically caused by traefik not matching the host header you are visiting it with. Do you have CF or anything in front of traefik?

If not confirm that your resources match the domain you are trying to visit them with.

Otherwise I would say you could edit the docker compose file to expose traefik port 8080 to see its dashboard and make sure that the routers are there and match the domain you are trying to visit.

If all of that looks good report back with the logs and we can dive deeper.

[LeonvanHeerden]

I had a similar issue and I found that I added the Resource for the HTTPS address, to the incorrect Site. It has to be the NEWT Site that will be handling the connection. In your case the one on the LCX/Docker/Proxmox.

I also had Rules enabled that didn't allow me to connection. Then I got an unauthorized connection. I turned off the rules to get it to work.
Still need to figure out how to add the rules to allow only my Ip ranges where I am connecting from, I think I had to add the external IP to get it to work, but that is not a viable solution for production. I should probably be using a NEWT or Wireguard connection as my source.

[miloschwartz]

@LeonvanHeerden We kicked around the idea of having Newt act as a DDNS agent and update the rule. I like this idea, but not sure where it fits in the development timeline right now.

[exhils]

I also found the same problem. But I have a different story. I have my own hardware. I have a static ip address. Virtualization is on the hardware. There are a couple of sites running on one ubuntu, and pangolin is on the other ubuntu. There is a router in front of the hardware. I have completed port forwarding. On a virtual machine where apache used a proxy to transfer 80 and 443 via the internal locale, forwarding works. But it gives out a 404. I tried to log in to the local network through windows by writing the address in the Hosts, everything worked, but it shouldn't be like that, how do I get it from outside?

[exhils]

So I suffered for 6 hours, complained and the problem was solved.

In Traefik, I changed my domain to a local ip and everything worked. I'll keep looking for problems)