github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 13:19:07 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

Resource Subdomain Not Sticking in UI or Backend; Only Root Domain is Used #519

New Issue
Closed
opened 2025-11-13 12:03:06 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-13 12:03:06 -06:00
Owner
Copy Link

Originally created by @erictwo on GitHub (Jul 23, 2025).

Pangolin Version

v1.7.3 Community Edition

Describe the Bug

When I create a Resource for a subdomain (e.g. nextcloud.profloors.cloud) via the UI:

  • The UI lets me type/select the subdomain during resource creation.
  • In the resource list and after saving, it always shows the root domain (e.g. https://profloors.cloud).
  • The resource URL never updates to the correct subdomain.
  • Accessing the subdomain from WAN does not work; only root domain seems to map.
  • I have verified my DNS is correct (wildcard A record and required entries).

Steps to Reproduce

  1. Set up Pangolin with wildcard DNS.
  2. Add a resource using nextcloud.profloors.cloud as the domain.
  3. Save and observe the Resource page still lists only the root domain.
  4. Try to access nextcloud.profloors.cloud from WAN — results in 404 or server not found.
  5. Editing the resource and re-saving does not fix the mapping.

What I Tried

  • Deleting and recreating the resource.
  • Removing all but wildcard/pangolin A records from DNS.
  • Manually editing resource via UI and restarting service.
  • Verified that config file does not have the subdomain (see below).

What Should Happen

The UI and backend should retain the full subdomain for the resource, and allow access via that subdomain, not just the root domain.

Notes

  • I have reviewed docs and several YouTube tutorials — subdomains are claimed to work with only wildcard DNS and a single A record.
  • No similar open Github issues found for 1.7.3, but community mentions on Reddit/YouTube.

Thanks for your help! Let me know if you need config, logs, or additional testing.

Image Image Image Image Image Image Image Image Image
Originally created by @erictwo on GitHub (Jul 23, 2025). ## Pangolin Version v1.7.3 Community Edition ## Describe the Bug When I create a Resource for a subdomain (e.g. `nextcloud.profloors.cloud`) via the UI: - The UI lets me type/select the subdomain during resource creation. - In the resource list and after saving, it always shows the root domain (e.g. `https://profloors.cloud`). - The resource URL never updates to the correct subdomain. - Accessing the subdomain from WAN does not work; only root domain seems to map. - I have verified my DNS is correct (wildcard A record and required entries). ## Steps to Reproduce 1. Set up Pangolin with wildcard DNS. 2. Add a resource using `nextcloud.profloors.cloud` as the domain. 3. Save and observe the Resource page still lists only the root domain. 4. Try to access `nextcloud.profloors.cloud` from WAN — results in 404 or server not found. 5. Editing the resource and re-saving does not fix the mapping. ## What I Tried - Deleting and recreating the resource. - Removing all but wildcard/pangolin A records from DNS. - Manually editing resource via UI and restarting service. - Verified that config file does not have the subdomain (see below). ## What Should Happen The UI and backend should retain the full subdomain for the resource, and allow access via that subdomain, not just the root domain. ## Notes - I have reviewed docs and several YouTube tutorials — subdomains are claimed to work with only wildcard DNS and a single A record. - No similar open Github issues found for 1.7.3, but community mentions on Reddit/YouTube. --- **Thanks for your help! Let me know if you need config, logs, or additional testing.** <!-- Failed to upload "1LAURA DESKTOP.zip" --> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/5a3b72d7-e2dd-441a-b04c-6b9264f34ddf" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/7f206439-aff0-45af-a43e-c062e322ed2b" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/55757d46-6d99-4f16-b85b-29b6c02768d2" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/e9db1cb4-d434-4322-90bb-691a6fdbadf8" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/1e02fa43-e80f-4d30-a6df-af20fa680d58" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/2e550b44-cf1d-4e3a-9d7d-1ebdb934f226" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/0cdb776f-61b7-4905-aea4-a68ae78c25b3" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/4a09c811-a0aa-40a7-bb70-72ebac80cd6f" /> <img width="3658" height="1740" alt="Image" src="https://github.com/user-attachments/assets/4bbb88b3-3b6c-4990-9048-7162663292b3" />
GiteaMirror commented 2025-11-13 12:03:07 -06:00
Author
Owner
Copy Link

@Tim5965 commented on GitHub (Jul 24, 2025):

Same problem with creating a new resource, only after creating you can set the correct address again and then it should work.

@Tim5965 commented on GitHub (Jul 24, 2025): Same problem with creating a new resource, only after creating you can set the correct address again and then it should work.
GiteaMirror commented 2025-11-13 12:03:07 -06:00
Author
Owner
Copy Link

@erictwo commented on GitHub (Jul 24, 2025):

Thanks so much Tim. That made it work

@erictwo commented on GitHub (Jul 24, 2025): Thanks so much Tim. That made it work
GiteaMirror commented 2025-11-13 12:03:07 -06:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Jul 24, 2025):

@Tim5965 @erictwo Thanks will look for the root cause of this.

@miloschwartz commented on GitHub (Jul 24, 2025): @Tim5965 @erictwo Thanks will look for the root cause of this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#519
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?