mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2314] [Chaching] Ctrl+F5 does not help - New DNS Provider doesn't show up in the frontend after updating docker compose #1642
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1642
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @knoxell on GitHub (Oct 9, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2314
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
I updated my
docker-compose.ymlfromjc21/nginx-proxy-manager:github-pr-2272tojc21/nginx-proxy-manager:github-pr-3212#3212 only adds a new certbot plugin requested in #2086.
The new DNS Provider doesn't show up in the frontend. Not even deleting the container and
docker compose uphelp.Spinning up a new container and logging into the admin UI, the added certbot-plugin shows up, when adding a new Let's Encrypt Certificate with
Nginx Proxy Manager Version
v2.9.18
To Reproduce
Steps to reproduce the behavior:
jc21/nginx-proxy-manager:github-pr-2272with certificates and proxy rules with compose file as pasted below.jc21/nginx-proxy-manager:github-pr-3212in compose file.Expected behavior
updating the docker compose file and redeploying npm with it should update the frontend
jc21/nginx-proxy-manager:github-pr-2272with certificates and proxy rules with compose file as pasted below.jc21/nginx-proxy-manager:github-pr-3212in compose file.Operating System
Debian Bullseye
Additional context
My
docker-compose.ymlMy
docker ps:@knoxell commented on GitHub (Oct 9, 2022):
I also get this warning importing my
/etc/letsencryptand/datafrom the newer newly created container with certs requested from namecheap into the old container, that should be on the same version.The logs don't say anything
@knoxell commented on GitHub (Oct 9, 2022):
Okay I changed the port mapping from the original
127.0.0.1:8111:81to127.0.0.1:3011:81and everything works fine, I am so confused and I would appreciate it if someone would explain to me why this is working now.That changing the port helped means this was a caching issue
right?but I reloaded the page withCtrl+F5and it did not help.Is this still a bug?
Edit:
Okay I changed the port back to the old
8111, and my UI doesn't show the plugin again. Opening the web UI in a private window (incognito mode for firefox users) results in me having Namecheap as an option.@knoxell commented on GitHub (Oct 9, 2022):
I guess this is a close and please refer to #1749 issue.
What happend in the screenshot above I'd know.