Locked out of resources page "http://..../settings/resources" after presumably wrong usage of Docker labels — Fully self-hosted instance #838

Closed
opened 2026-04-05 17:51:28 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @maxiride on 9/29/2025

Describe the Bug

I successfully setup and used Pangolin on a VPS. Till now, I manually added resources through the web ui, but I decided to try docker labels for automatic provisioning of new resources since I am transitioning away from caddy's lucaslorentz image. This image does the same thing for Caddy through labels.

I created a basic whoami container with the following label:

pangolin.proxy-resources.full-domain: whoami.mydomain.tld
pangolin.proxy-resources.targets[0].method: http

After reloading the newt container to apply the blueprint I can't access my Pangolin resources page.

Image

The developer tools report Uncaught TypeError: can't access property "toString", r.proxyPort is null:

Image

I tried to stop the whoami container, remove the labels etc but I can't regain access to Pangolin resources page. I know from the officical Youtube video that resources are not automatically deleted, however I am not understanding what to manipulate in Pangolin's local files configuration to remove the resource backend-side.

So the issue is tri-fold:

  1. Regain access to Pangolin resources page
  2. Understand/fix the documentation
  3. If the labels are indeed incorrect because I did not understand the docs: improve newt/Pangolin to refuse an incomplete docker label definition instead of locking out the user.

According to the documentation, or at least my understanding of it, these are the only required fields when creating a target only resource.

The configuration table reports that:

  • Automatic Discovery
    When hostname and internal port are not explicitly defined in labels, Pangolin will automatically detect them from the container configuration.

  • Site Assignment
    If no site is specified in the labels, the resource will be assigned to the Newt site that discovered the container.

Image Image

Environment

  • OS Type & Version: Ubuntu 22.04
  • Pangolin Version: 1.10.2
  • Gerbil Version: fosrl/gerbil:1.2.1
  • Traefik Version: v3.5
  • Newt Version: 1.5.1

To Reproduce

  1. Spin up a Pangolin docker stack
  2. Add a newt node to a server
  3. Create a container with labels as described above
  4. Restart newt (seems like it doesn't automatically detect changes/new containers)
  5. Open Pangolin dashboard and open the resources page
  6. Observe the error

Expected Behavior

I expected either Newt to refuse the container's labels with an error in the logs, or the resource to not appear in the Pangolin dashboard.

*Originally created by @maxiride on 9/29/2025* ### Describe the Bug I successfully setup and used Pangolin on a VPS. Till now, I manually added resources through the web ui, but I decided to try docker labels for automatic provisioning of new resources since I am transitioning away from caddy's lucaslorentz image. This image does the same thing for Caddy through labels. I created a basic [whoami](https://hub.docker.com/r/containous/whoami/) container with the following label: ``` pangolin.proxy-resources.full-domain: whoami.mydomain.tld pangolin.proxy-resources.targets[0].method: http ``` After reloading the `newt` container to apply the blueprint I can't access my Pangolin resources page. <img width="2024" height="1344" alt="Image" src="https://github.com/user-attachments/assets/efa43671-9a30-4532-972e-e361aff6c5d6" /> The developer tools report `Uncaught TypeError: can't access property "toString", r.proxyPort is null`: <img width="1669" height="62" alt="Image" src="https://github.com/user-attachments/assets/f5a757d5-ef8e-4d61-b746-ae61578b24c4" /> I tried to stop the `whoami` container, remove the labels etc but I can't regain access to Pangolin resources page. I know from the [officical Youtube video](https://www.youtube.com/watch?v=lMauwwitSAE) that resources are not automatically deleted, however I am not understanding what to manipulate in Pangolin's local files configuration to remove the resource backend-side. **So the issue is tri-fold:** 1. Regain access to Pangolin resources page 2. Understand/fix the documentation 3. If the labels are indeed incorrect because I did not understand the docs: improve newt/Pangolin to refuse an incomplete docker label definition instead of locking out the user. --- According to the [documentation](https://docs.digpangolin.com/manage/blueprints), or at least my understanding of it, these are the only required fields when creating a target only resource. The [configuration table](https://docs.digpangolin.com/manage/blueprints#configuration-properties) reports that: - Automatic Discovery When **hostname** and **internal port** are not explicitly defined in labels, **Pangolin will automatically detect them from the container configuration.** - Site Assignment If no site is specified in the labels, **the resource will be assigned to the Newt site that discovered the container.** <img width="1003" height="974" alt="Image" src="https://github.com/user-attachments/assets/5524ff9c-ff27-4dbe-8423-a7398ac77bfd" /> <img width="979" height="624" alt="Image" src="https://github.com/user-attachments/assets/4aa99c1f-f433-4a85-af34-a80dc42dc3ea" /> ### Environment - OS Type & Version: Ubuntu 22.04 - Pangolin Version: 1.10.2 - Gerbil Version: fosrl/gerbil:1.2.1 - Traefik Version: v3.5 - Newt Version: 1.5.1 ### To Reproduce 1. Spin up a Pangolin docker stack 2. Add a newt node to a server 3. Create a container with labels as described above 4. Restart newt (seems like it doesn't automatically detect changes/new containers) 5. Open Pangolin dashboard and open the resources page 6. Observe the error ### Expected Behavior I expected either Newt to refuse the container's labels with an error in the logs, or the resource to not appear in the Pangolin dashboard.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#838