Feature Request: Managing Domains in UI #1427

New Issue

MrUnknownDE · 2026-04-05T19:28:05+02:00

MrUnknownDE commented

2026-04-05 19:28:05 +02:00

Originally created by @kalikid021 on 5/31/2025

From what I can see, adding an additional domain to Pangolin, requires editing the config.yml however after making that change, I cannot just re-run docker compose up -d and have the stack pickup the new domain in the config. I have to bring down the full stack with docker compose down and then bring the stack back up in order for the config change to take effect.

This creates issues and inconsistencies when running services through Pangolin. This wouldn't be considered a "mission critical" capable application, if the application needs to be taken offline each time a configuration change needs to be made.

I imagine this has more to do with Traefik than pangolin, but being able to make changes to the domain structure seems like a core component of the application, and managing those changes in the UI, and having Traefik reload the config upon clicking save in the Pangolin UI, would be ideal as opposed to the current process. Also managing Traefik from the Pangolin UI (as it's also a core component) would be an ideal addition as well.

Hopefully this gets put on the roadmap. I really like the software, and it is very promising. I'm looking forward to replacing CF Tunnels with it, and have been slowly integrating it into my secondary home lab services. I'm not ready to move things like IDP/Auth over yet due to the feature request. I am looking forward to it's continued progress and development.

*Originally created by @kalikid021 on 5/31/2025* From what I can see, adding an additional domain to Pangolin, requires editing the config.yml however after making that change, I cannot just re-run `docker compose up -d` and have the stack pickup the new domain in the config. I have to bring down the full stack with `docker compose down` and then bring the stack back up in order for the config change to take effect. This creates issues and inconsistencies when running services through Pangolin. This wouldn't be considered a "mission critical" capable application, if the application needs to be taken offline each time a configuration change needs to be made. I imagine this has more to do with Traefik than pangolin, but being able to make changes to the domain structure seems like a core component of the application, and managing those changes in the UI, and having Traefik reload the config upon clicking save in the Pangolin UI, would be ideal as opposed to the current process. Also managing Traefik from the Pangolin UI (as it's also a core component) would be an ideal addition as well. Hopefully this gets put on the roadmap. I really like the software, and it is very promising. I'm looking forward to replacing CF Tunnels with it, and have been slowly integrating it into my secondary home lab services. I'm not ready to move things like IDP/Auth over yet due to the feature request. I am looking forward to it's continued progress and development.

MrUnknownDE closed this issue

2026-04-05 19:28:05 +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#1427