public-resources and private-resources dont trigger blueprint updates #456

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

Originally created by @angelrwu on 12/19/2025

Describe the Bug

If you make a blueprint that uses public-resources instead of proxy-resources or private-resources instead of client-resources. The pangolin blueprint updater doesn't trigger and will output that an empty list of items was successfully updated "[]"

I believe the bug is related to this section https://github.com/fosrl/pangolin/blob/main/server/lib/blueprints/applyNewtDockerBlueprint.ts#L37-L40 or this https://github.com/fosrl/pangolin/blob/main/server/lib/blueprints/parseDockerContainers.ts#L54-L61
, but I'm unsure.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04)
  • Pangolin Version: 1.13.1
  • Gerbil Version: 1.2.1
  • Traefik Version: 3.6.1
  • Newt Version: 1.5.2
  • Olm Version: (if applicable)

To Reproduce

Insert a minimal blueprint with public-resources key or private-resources to get the bad case, and to get the happy path replace those for client and proxy.

Set the logging to debug to see the console output for the newt blueprint message and the pangolin blueprint update message

examples:

bad output when public and private resource are the key in blueprint

Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.812Z [debug]: Received blueprint: {"public-resources":{"testss-resource":{"full-domain":"testss.example.com","name":"tests-name","protocol":"http"}}}
Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.813Z [debug]: Successfully updated proxy resources for org example: []
Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.814Z [debug]: Successfully updated client resources for org example: []

good output when proxy and client resource are the key in blueprint

Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.292Z [debug]: Received blueprint: {"proxy-resources":{"tests-resource":{"full-domain":"tests.example.com","name":"tests-name","protocol":"http"}}}
Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.315Z [debug]: Created resource 4
Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.316Z [debug]: Successfully updated proxy resources for org example: [{"proxyResource":{"resourceId":4,"orgId":"example","niceId":"tests-resource","name":"tests-name","subdomain":null,"fullDomain":"tests.example.com","domainId":"domain1","ssl":true,"blockAccess":false,"sso":false,"http":true,"protocol":"tcp","proxyPort":null,"emailWhitelistEnabled":false,"applyRules":false,"enabled":true,"stickySession":false,"tlsServerName":null,"setHostHeader":null,"enableProxy":true,"skipToIdpId":null,"headers":null},"targetsToUpdate":[]}]
Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.317Z [debug]: Successfully updated client resources for org example: **[]**

Expected Behavior

Public and private resources key should trigger Pangolin to do resource updates or additions.
Alternatively the docs should be updated not to use public and private and use proxy and client, which would match the UI.

*Originally created by @angelrwu on 12/19/2025* ### Describe the Bug If you make a blueprint that uses `public-resources` instead of `proxy-resources` or `private-resources` instead of `client-resources`. The pangolin blueprint updater doesn't trigger and will output that an empty list of items was successfully updated "[]" I believe the bug is related to this section https://github.com/fosrl/pangolin/blob/main/server/lib/blueprints/applyNewtDockerBlueprint.ts#L37-L40 or this https://github.com/fosrl/pangolin/blob/main/server/lib/blueprints/parseDockerContainers.ts#L54-L61 , but I'm unsure. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: 1.13.1 - Gerbil Version: 1.2.1 - Traefik Version: 3.6.1 - Newt Version: 1.5.2 - Olm Version: (if applicable) ### To Reproduce Insert a minimal blueprint with public-resources key or private-resources to get the bad case, and to get the happy path replace those for client and proxy. Set the logging to debug to see the console output for the newt blueprint message and the pangolin blueprint update message examples: bad output when public and private resource are the key in blueprint ``` Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.812Z [debug]: Received blueprint: {"public-resources":{"testss-resource":{"full-domain":"testss.example.com","name":"tests-name","protocol":"http"}}} Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.813Z [debug]: Successfully updated proxy resources for org example: [] Dec 19 04:27:19 <hostname> pangolin[3772]: 2025-12-19T04:27:19.814Z [debug]: Successfully updated client resources for org example: [] ``` good output when proxy and client resource are the key in blueprint ``` Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.292Z [debug]: Received blueprint: {"proxy-resources":{"tests-resource":{"full-domain":"tests.example.com","name":"tests-name","protocol":"http"}}} Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.315Z [debug]: Created resource 4 Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.316Z [debug]: Successfully updated proxy resources for org example: [{"proxyResource":{"resourceId":4,"orgId":"example","niceId":"tests-resource","name":"tests-name","subdomain":null,"fullDomain":"tests.example.com","domainId":"domain1","ssl":true,"blockAccess":false,"sso":false,"http":true,"protocol":"tcp","proxyPort":null,"emailWhitelistEnabled":false,"applyRules":false,"enabled":true,"stickySession":false,"tlsServerName":null,"setHostHeader":null,"enableProxy":true,"skipToIdpId":null,"headers":null},"targetsToUpdate":[]}] Dec 19 04:26:25 <hostname> pangolin[3772]: 2025-12-19T04:26:25.317Z [debug]: Successfully updated client resources for org example: **[]** ``` ### Expected Behavior Public and private resources key should trigger Pangolin to do resource updates or additions. Alternatively the docs should be updated not to use public and private and use proxy and client, which would match the UI.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#456