[GH-ISSUE #2314] [Chaching] Ctrl+F5 does not help - New DNS Provider doesn't show up in the frontend after updating docker compose #1642

Closed
opened 2026-02-26 07:31:53 +03:00 by kerem · 3 comments
Owner

Originally created by @knoxell on GitHub (Oct 9, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2314

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • No
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

I updated my docker-compose.yml from jc21/nginx-proxy-manager:github-pr-2272 to jc21/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 up help.

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

docker run -p 127.0.0.1:3081:81 jc21/nginx-proxy-manager:github-pr-3212

Nginx Proxy Manager Version

v2.9.18

To Reproduce
Steps to reproduce the behavior:

  • Use jc21/nginx-proxy-manager:github-pr-2272 with certificates and proxy rules with compose file as pasted below.
  • update tag to jc21/nginx-proxy-manager:github-pr-3212 in compose file.
  • Add new Let's Encrypt Certificate.
    • Choose DNS Provider
    • Namecheap is not an option

Expected behavior

updating the docker compose file and redeploying npm with it should update the frontend

  • Use jc21/nginx-proxy-manager:github-pr-2272 with certificates and proxy rules with compose file as pasted below.
  • update tag to jc21/nginx-proxy-manager:github-pr-3212 in compose file.
  • Add new Let's Encrypt Certificate.
    • Choose DNS Provider
    • Namecheap is an option as if I created a new container

Operating System

Debian Bullseye

Additional context

My docker-compose.yml

version: '3'
services:
  app:
    container_name: nginxproxymanager
    image: 'jc21/nginx-proxy-manager:github-pr-2312' # the only change happend here
    restart: unless-stopped
    ports:
      - '80:80'
      - '127.0.0.1:8111:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
networks:
  default:
    name: reverseproxy

My docker ps :

CONTAINER ID   IMAGE                                     COMMAND                  CREATED          STATUS         PORTS
                      NAMES
c5bd39d22a6b   jc21/nginx-proxy-manager:github-pr-2312   "/init"                  7 minutes ago    Up 6 minutes   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 127.0.0.1:8111->81/tcp   nginxproxymanager
c8c1f7981cd8   jc21/nginx-proxy-manager:github-pr-2312   "/init"                  54 minutes ago   Up 4 minutes   80/tcp, 443/tcp, 127.0.0.1:3081->81/tcp
Originally created by @knoxell on GitHub (Oct 9, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2314 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> I updated my `docker-compose.yml` from `jc21/nginx-proxy-manager:github-pr-2272` to `jc21/nginx-proxy-manager:github-pr-3212` [#3212](https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2312) 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 up` help. 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 ``` docker run -p 127.0.0.1:3081:81 jc21/nginx-proxy-manager:github-pr-3212 ``` **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.9.18 **To Reproduce** Steps to reproduce the behavior: - Use `jc21/nginx-proxy-manager:github-pr-2272` with certificates and proxy rules with compose file as pasted below. - update tag to `jc21/nginx-proxy-manager:github-pr-3212` in compose file. - Add new Let's Encrypt Certificate. - Choose DNS Provider - Namecheap is not an option **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> updating the docker compose file and redeploying npm with it should update the frontend - Use `jc21/nginx-proxy-manager:github-pr-2272` with certificates and proxy rules with compose file as pasted below. - update tag to `jc21/nginx-proxy-manager:github-pr-3212` in compose file. - Add new Let's Encrypt Certificate. - Choose DNS Provider - Namecheap is an option as if I created a new container **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Debian Bullseye **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> My `docker-compose.yml` ```yaml version: '3' services: app: container_name: nginxproxymanager image: 'jc21/nginx-proxy-manager:github-pr-2312' # the only change happend here restart: unless-stopped ports: - '80:80' - '127.0.0.1:8111:81' - '443:443' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt networks: default: name: reverseproxy ``` My `docker ps` : ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c5bd39d22a6b jc21/nginx-proxy-manager:github-pr-2312 "/init" 7 minutes ago Up 6 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 127.0.0.1:8111->81/tcp nginxproxymanager c8c1f7981cd8 jc21/nginx-proxy-manager:github-pr-2312 "/init" 54 minutes ago Up 4 minutes 80/tcp, 443/tcp, 127.0.0.1:3081->81/tcp ```
kerem 2026-02-26 07:31:53 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@knoxell commented on GitHub (Oct 9, 2022):

pic-selected-221009-2022-13
I also get this warning importing my /etc/letsencrypt and /data from 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

Attaching to nginxproxymanager-npm-1
nginxproxymanager-npm-1  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
nginxproxymanager-npm-1  | [s6-init] ensuring user provided files have correct perms...exited 0.
nginxproxymanager-npm-1  | [fix-attrs.d] applying ownership & permissions fixes...
nginxproxymanager-npm-1  | [fix-attrs.d] done.
nginxproxymanager-npm-1  | [cont-init.d] executing container initialization scripts...
nginxproxymanager-npm-1  | [cont-init.d] 01_perms.sh: executing...
nginxproxymanager-npm-1  | Changing ownership of /data/logs to 0:0
nginxproxymanager-npm-1  | [cont-init.d] 01_perms.sh: exited 0.
nginxproxymanager-npm-1  | [cont-init.d] 01_s6-secret-init.sh: executing...
nginxproxymanager-npm-1  | [cont-init.d] 01_s6-secret-init.sh: exited 0.
nginxproxymanager-npm-1  | [cont-init.d] done.
nginxproxymanager-npm-1  | [services.d] starting services
nginxproxymanager-npm-1  | [services.d] done.
nginxproxymanager-npm-1  | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/default.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/proxy.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/assets.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/force-ssl.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/block-exploits.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/ip_ranges.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/include/resolvers.conf
nginxproxymanager-npm-1  |   ❯ /etc/nginx/conf.d/production.conf
nginxproxymanager-npm-1  | ❯ Enabling IPV6 in hosts: /data/nginx
nginxproxymanager-npm-1  |   ❯ /data/nginx/default_host/site.conf
nginxproxymanager-npm-1  | [10/9/2022] [6:13:41 PM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
nginxproxymanager-npm-1  | [10/9/2022] [6:13:41 PM] [Global   ] › ℹ  info      Generating SQLite knex configuration
nginxproxymanager-npm-1  | [10/9/2022] [6:13:41 PM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
nginxproxymanager-npm-1  | [10/9/2022] [6:13:41 PM] [Migrate  ] › ℹ  info      Current database version: none
nginxproxymanager-npm-1  | [10/9/2022] [6:13:42 PM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
nginxproxymanager-npm-1  | [10/9/2022] [6:13:46 PM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [Setup    ] › ℹ  info      Added Certbot plugins certbot-dns-namecheap~=1.0.0
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [Setup    ] › ℹ  info      Logrotate completed.
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
nginxproxymanager-npm-1  | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
nginxproxymanager-npm-1  | [10/9/2022] [6:14:00 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
nginxproxymanager-npm-1  | [10/9/2022] [6:14:00 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
nginxproxymanager-npm-1  | [10/9/2022] [6:14:00 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
nginxproxymanager-npm-1  | [10/9/2022] [6:14:00 PM] [Global   ] › ℹ  info      Backend PID 253 listening on port 3000 ...
nginxproxymanager-npm-1  | [10/9/2022] [6:14:01 PM] [Nginx    ] › ℹ  info      Reloading Nginx
nginxproxymanager-npm-1  | [10/9/2022] [6:14:01 PM] [SSL      ] › ℹ  info      Renew Complete
nginxproxymanager-npm-1  | `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
nginxproxymanager-npm-1  | `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
nginxproxymanager-npm-1  | QueryBuilder#omit is deprecated. This method will be removed in version 3.0
nginxproxymanager-npm-1  | Model#$omit is deprected and will be removed in 3.0.
<!-- gh-comment-id:1272601378 --> @knoxell commented on GitHub (Oct 9, 2022): ![pic-selected-221009-2022-13](https://user-images.githubusercontent.com/85034894/194773145-4c83cafd-2fea-444b-a801-18b7b4ff4f09.png) I also get this warning importing my `/etc/letsencrypt` and `/data` from 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 ``` Attaching to nginxproxymanager-npm-1 nginxproxymanager-npm-1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0. nginxproxymanager-npm-1 | [s6-init] ensuring user provided files have correct perms...exited 0. nginxproxymanager-npm-1 | [fix-attrs.d] applying ownership & permissions fixes... nginxproxymanager-npm-1 | [fix-attrs.d] done. nginxproxymanager-npm-1 | [cont-init.d] executing container initialization scripts... nginxproxymanager-npm-1 | [cont-init.d] 01_perms.sh: executing... nginxproxymanager-npm-1 | Changing ownership of /data/logs to 0:0 nginxproxymanager-npm-1 | [cont-init.d] 01_perms.sh: exited 0. nginxproxymanager-npm-1 | [cont-init.d] 01_s6-secret-init.sh: executing... nginxproxymanager-npm-1 | [cont-init.d] 01_s6-secret-init.sh: exited 0. nginxproxymanager-npm-1 | [cont-init.d] done. nginxproxymanager-npm-1 | [services.d] starting services nginxproxymanager-npm-1 | [services.d] done. nginxproxymanager-npm-1 | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/default.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/proxy.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/assets.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/force-ssl.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/block-exploits.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/ip_ranges.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/include/resolvers.conf nginxproxymanager-npm-1 | ❯ /etc/nginx/conf.d/production.conf nginxproxymanager-npm-1 | ❯ Enabling IPV6 in hosts: /data/nginx nginxproxymanager-npm-1 | ❯ /data/nginx/default_host/site.conf nginxproxymanager-npm-1 | [10/9/2022] [6:13:41 PM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' nginxproxymanager-npm-1 | [10/9/2022] [6:13:41 PM] [Global ] › ℹ info Generating SQLite knex configuration nginxproxymanager-npm-1 | [10/9/2022] [6:13:41 PM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json nginxproxymanager-npm-1 | [10/9/2022] [6:13:41 PM] [Migrate ] › ℹ info Current database version: none nginxproxymanager-npm-1 | [10/9/2022] [6:13:42 PM] [Setup ] › ℹ info Creating a new JWT key pair... nginxproxymanager-npm-1 | [10/9/2022] [6:13:46 PM] [Setup ] › ℹ info Wrote JWT key pair to config file: /app/config/production.json nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [Setup ] › ℹ info Added Certbot plugins certbot-dns-namecheap~=1.0.0 nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [Setup ] › ℹ info Logrotate Timer initialized nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [Setup ] › ℹ info Logrotate completed. nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 nginxproxymanager-npm-1 | [10/9/2022] [6:13:59 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 nginxproxymanager-npm-1 | [10/9/2022] [6:14:00 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized nginxproxymanager-npm-1 | [10/9/2022] [6:14:00 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... nginxproxymanager-npm-1 | [10/9/2022] [6:14:00 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized nginxproxymanager-npm-1 | [10/9/2022] [6:14:00 PM] [Global ] › ℹ info Backend PID 253 listening on port 3000 ... nginxproxymanager-npm-1 | [10/9/2022] [6:14:01 PM] [Nginx ] › ℹ info Reloading Nginx nginxproxymanager-npm-1 | [10/9/2022] [6:14:01 PM] [SSL ] › ℹ info Renew Complete nginxproxymanager-npm-1 | `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 nginxproxymanager-npm-1 | `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 nginxproxymanager-npm-1 | QueryBuilder#omit is deprecated. This method will be removed in version 3.0 nginxproxymanager-npm-1 | Model#$omit is deprected and will be removed in 3.0. ```
Author
Owner

@knoxell commented on GitHub (Oct 9, 2022):

Okay I changed the port mapping from the original 127.0.0.1:8111:81 to 127.0.0.1:3011:81 and 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 with Ctrl+F5 and 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.

<!-- gh-comment-id:1272605415 --> @knoxell commented on GitHub (Oct 9, 2022): Okay I changed the port mapping from the original `127.0.0.1:8111:81` to `127.0.0.1:3011:81` and 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 with `Ctrl+F5` and 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.
Author
Owner

@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.

<!-- gh-comment-id:1272608533 --> @knoxell commented on GitHub (Oct 9, 2022): I guess this is a close and please refer to [#1749](https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1749#user-content-admin-page-blank-or-weird) issue. What happend in the screenshot above I'd know.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1642
No description provided.