Cannot Proxy Docker Containers Running Alongside Pangolin in the VPS #1557

New Issue

MrUnknownDE · 2026-04-05T19:34:27+02:00

MrUnknownDE commented

2026-04-05 19:34:27 +02:00

Originally created by @epoch-philosophy on 4/29/2025

Hey all, this may be a pretty dumb one. But, I have a single VPS that houses Pangolin. It also contains some monitoring containers like Ntfy and Uptime-Kuma. I keep those on a VPS because my cat likes to turn off my local machines here and there and still want to get notifications in case she turned off the server housing Uptime-Kuma! (She's done this many times.)

The problem:

I cannot get Pangolin to properly proxy Uptime-Kuma (or any other local docker container on the VPS). I've tried via the "local" site connection, and even deployed a Newt connection on the same VPS. No avail.

I made sure to have the Uptime-Kuma container on the Pangolin network, used the public IP as the http source. I used it's docker IP, it's docker host name, and everything else I can think of.

I have a feeling I may need to route internal containers through Traefik as an external route/service in the dynamic_config.yml, but wanted to check first here, as there's no official documentation.

(Also know it's probably best practice to have a dedicated VPS for Pangolin.)

*Originally created by @epoch-philosophy on 4/29/2025* Hey all, this may be a pretty dumb one. But, I have a single VPS that houses Pangolin. It also contains some monitoring containers like Ntfy and Uptime-Kuma. I keep those on a VPS because my cat likes to turn off my local machines here and there and still want to get notifications in case she turned off the server housing Uptime-Kuma! (She's done this many times.) The problem: I cannot get Pangolin to properly proxy Uptime-Kuma (or any other local docker container on the VPS). I've tried via the "local" site connection, and even deployed a Newt connection on the same VPS. No avail. I made sure to have the Uptime-Kuma container on the Pangolin network, used the public IP as the http source. I used it's docker IP, it's docker host name, and everything else I can think of. I have a feeling I may need to route internal containers through Traefik as an external route/service in the dynamic_config.yml, but wanted to check first here, as there's no official documentation. (Also know it's probably best practice to have a dedicated VPS for Pangolin.)

MrUnknownDE closed this issue

2026-04-05 19:34:27 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1557