[GH-ISSUE #1219] Upgraded to v2.9.4 - frontend no longer usable #993

New issue

Open

opened 2026-02-26 06:35:20 +03:00 by kerem · 15 comments

kerem commented 2026-02-26 06:35:20 +03:00

Owner

Copy link

Originally created by @danner26 on GitHub (Jul 4, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1219

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• 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 am running NPM using docker-compse. where I ran docker-compose pull and then docker-compose up -d
When the app started, I logged into the new version and instead of having the dashboard/proxy hosts I cannot see anything. I check the Chrome console tab and see a bunch of these:

Welcome to Nginx Proxy Manager
main.bundle.js?v=2.9.4:3 You are logged in as Daniel Anner
main.bundle.js?v=2.9.4:1 TypeError: Cannot read property 'extend' of undefined
    at Object.213 (7.bundle.7.js:1)
    at r (main.bundle.js?v=2.9.4:1)
    at Object.181 (7.bundle.7.js:1)
    at r (main.bundle.js?v=2.9.4:1)
    at main.bundle.js?v=2.9.4:27
r.oe @ main.bundle.js?v=2.9.4:1
Promise.catch (async)
showNginxProxy @ main.bundle.js?v=2.9.4:27
Ze @ main.bundle.js?v=2.9.4:3
(anonymous) @ main.bundle.js?v=2.9.4:3
(anonymous) @ main.bundle.js?v=2.9.4:3
execute @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:27
Ct @ main.bundle.js?v=2.9.4:3
loadUrl @ main.bundle.js?v=2.9.4:27
start @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:3
m @ main.bundle.js?v=2.9.4:27
f @ main.bundle.js?v=2.9.4:27
d @ main.bundle.js?v=2.9.4:27
o.trigger @ main.bundle.js?v=2.9.4:27
O @ main.bundle.js?v=2.9.4:27
render @ main.bundle.js?v=2.9.4:27
ae @ main.bundle.js?v=2.9.4:27
show @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:3
Promise.then (async)
onStart @ main.bundle.js?v=2.9.4:3
O @ main.bundle.js?v=2.9.4:27
start @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:293
d @ main.bundle.js?v=2.9.4:27
l @ main.bundle.js?v=2.9.4:27
setTimeout (async)
(anonymous) @ main.bundle.js?v=2.9.4:27
u @ main.bundle.js?v=2.9.4:27
fireWith @ main.bundle.js?v=2.9.4:27
fire @ main.bundle.js?v=2.9.4:27
u @ main.bundle.js?v=2.9.4:27
fireWith @ main.bundle.js?v=2.9.4:27
ready @ main.bundle.js?v=2.9.4:27
V @ main.bundle.js?v=2.9.4:27
7.bundle.7.js:1 Uncaught (in promise) TypeError: Cannot read property 'extend' of undefined
    at Object.213 (7.bundle.7.js:1)
    at r (main.bundle.js?v=2.9.4:1)
    at Object.181 (7.bundle.7.js:1)
    at r (main.bundle.js?v=2.9.4:1)
    at main.bundle.js?v=2.9.4:27

Nginx Proxy Manager Version
2.9.4

Screenshots

Operating System
Alpine Linux 3.13.5, Docker 20.10.3, Docker-Compose 1.27.4

Additional context
Logs: https://pastebin.com/swz7nvse

Originally created by @danner26 on GitHub (Jul 4, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1219 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - 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 am running NPM using docker-compse. where I ran `docker-compose pull` and then `docker-compose up -d` When the app started, I logged into the new version and instead of having the dashboard/proxy hosts I cannot see anything. I check the Chrome console tab and see a bunch of these: ``` Welcome to Nginx Proxy Manager main.bundle.js?v=2.9.4:3 You are logged in as Daniel Anner main.bundle.js?v=2.9.4:1 TypeError: Cannot read property 'extend' of undefined at Object.213 (7.bundle.7.js:1) at r (main.bundle.js?v=2.9.4:1) at Object.181 (7.bundle.7.js:1) at r (main.bundle.js?v=2.9.4:1) at main.bundle.js?v=2.9.4:27 r.oe @ main.bundle.js?v=2.9.4:1 Promise.catch (async) showNginxProxy @ main.bundle.js?v=2.9.4:27 Ze @ main.bundle.js?v=2.9.4:3 (anonymous) @ main.bundle.js?v=2.9.4:3 (anonymous) @ main.bundle.js?v=2.9.4:3 execute @ main.bundle.js?v=2.9.4:27 (anonymous) @ main.bundle.js?v=2.9.4:27 (anonymous) @ main.bundle.js?v=2.9.4:27 Ct @ main.bundle.js?v=2.9.4:3 loadUrl @ main.bundle.js?v=2.9.4:27 start @ main.bundle.js?v=2.9.4:27 (anonymous) @ main.bundle.js?v=2.9.4:3 m @ main.bundle.js?v=2.9.4:27 f @ main.bundle.js?v=2.9.4:27 d @ main.bundle.js?v=2.9.4:27 o.trigger @ main.bundle.js?v=2.9.4:27 O @ main.bundle.js?v=2.9.4:27 render @ main.bundle.js?v=2.9.4:27 ae @ main.bundle.js?v=2.9.4:27 show @ main.bundle.js?v=2.9.4:27 (anonymous) @ main.bundle.js?v=2.9.4:3 Promise.then (async) onStart @ main.bundle.js?v=2.9.4:3 O @ main.bundle.js?v=2.9.4:27 start @ main.bundle.js?v=2.9.4:27 (anonymous) @ main.bundle.js?v=2.9.4:293 d @ main.bundle.js?v=2.9.4:27 l @ main.bundle.js?v=2.9.4:27 setTimeout (async) (anonymous) @ main.bundle.js?v=2.9.4:27 u @ main.bundle.js?v=2.9.4:27 fireWith @ main.bundle.js?v=2.9.4:27 fire @ main.bundle.js?v=2.9.4:27 u @ main.bundle.js?v=2.9.4:27 fireWith @ main.bundle.js?v=2.9.4:27 ready @ main.bundle.js?v=2.9.4:27 V @ main.bundle.js?v=2.9.4:27 7.bundle.7.js:1 Uncaught (in promise) TypeError: Cannot read property 'extend' of undefined at Object.213 (7.bundle.7.js:1) at r (main.bundle.js?v=2.9.4:1) at Object.181 (7.bundle.7.js:1) at r (main.bundle.js?v=2.9.4:1) at main.bundle.js?v=2.9.4:27 ``` **Nginx Proxy Manager Version** 2.9.4 **Screenshots**  **Operating System** Alpine Linux 3.13.5, Docker 20.10.3, Docker-Compose 1.27.4 **Additional context** Logs: https://pastebin.com/swz7nvse

kerem added the

stale

bug

awaiting feedback

labels 2026-02-26 06:35:20 +03:00

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@danner26 commented on GitHub (Jul 4, 2021):

I also recreated the images to ensure it was built properly docker-compose up --force-recreate --build -d
That did not fix the issue

Here is my docker-compose.yml

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: _**REDACTED**_
      DB_MYSQL_PASSWORD: _**REDACTED**_
      DB_MYSQL_NAME: "nginx_proxy_manager"
      DISABLE_IPV6: 'true'
      X_FRAME_OPTIONS: "sameorigin"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
      - ./letsencrypt/logs:/var/log/letsencrypt/
  db:
    image: 'jc21/mariadb-aria:latest'
    environment:
      MYSQL_ROOT_PASSWORD: _**REDACTED**_
      MYSQL_DATABASE: _**REDACTED**_
      MYSQL_USER: _**REDACTED**_
      MYSQL_PASSWORD: _**REDACTED**_
      DISABLE_IPV6: 'true'
      X_FRAME_OPTIONS: "sameorigin"
    volumes:
      - ./data/mysql:/var/lib/mysql
networks:
  default:
    external:
      name: proxynet

<!-- gh-comment-id:873659491 --> @danner26 commented on GitHub (Jul 4, 2021): I also recreated the images to ensure it was built properly `docker-compose up --force-recreate --build -d` That did not fix the issue Here is my docker-compose.yml ``` version: '3' services: app: image: 'jc21/nginx-proxy-manager:latest' ports: - '80:80' - '81:81' - '443:443' environment: DB_MYSQL_HOST: "db" DB_MYSQL_PORT: 3306 DB_MYSQL_USER: _**REDACTED**_ DB_MYSQL_PASSWORD: _**REDACTED**_ DB_MYSQL_NAME: "nginx_proxy_manager" DISABLE_IPV6: 'true' X_FRAME_OPTIONS: "sameorigin" volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt - ./letsencrypt/logs:/var/log/letsencrypt/ db: image: 'jc21/mariadb-aria:latest' environment: MYSQL_ROOT_PASSWORD: _**REDACTED**_ MYSQL_DATABASE: _**REDACTED**_ MYSQL_USER: _**REDACTED**_ MYSQL_PASSWORD: _**REDACTED**_ DISABLE_IPV6: 'true' X_FRAME_OPTIONS: "sameorigin" volumes: - ./data/mysql:/var/lib/mysql networks: default: external: name: proxynet ```

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@danner26 commented on GitHub (Jul 4, 2021):

Just to ensure that the issue is not related to me being a smacker, I decided to fully shut down the containers, remove all images on the drive (that pertained to NPM), and do a full, fresh install (using the same data of course) and still no dice

Definitely a frontend issue in my opinion but I have no idea why if it is the latest stable release?

<!-- gh-comment-id:873661032 --> @danner26 commented on GitHub (Jul 4, 2021): Just to ensure that the issue is not related to me being a smacker, I decided to fully shut down the containers, remove all images on the drive (that pertained to NPM), and do a full, fresh install (using the same data of course) and still no dice Definitely a frontend issue in my opinion but I have no idea why if it is the latest stable release?

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@Nozza-VS commented on GitHub (Jul 6, 2021):

I just upgraded from 2.9.0 to 2.9.4 and encountered this briefly, quick browser cache refresh did the trick

<!-- gh-comment-id:874593713 --> @Nozza-VS commented on GitHub (Jul 6, 2021): I just upgraded from 2.9.0 to 2.9.4 and encountered this briefly, quick browser cache refresh did the trick

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@danner26 commented on GitHub (Jul 6, 2021):

Thanks @Nozza-VS unfortunately that isn't the fix for me. I've tried incognito windows and other browsers without success. The same behavior is experienced

<!-- gh-comment-id:874683610 --> @danner26 commented on GitHub (Jul 6, 2021): Thanks @Nozza-VS unfortunately that isn't the fix for me. I've tried incognito windows and other browsers without success. The same behavior is experienced

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@Ceriwaen commented on GitHub (Jul 10, 2021):

I just experienced this as well. Downgrading to 2.8.1 and refreshing browser cache returned it to functionality.

<!-- gh-comment-id:877678025 --> @Ceriwaen commented on GitHub (Jul 10, 2021): I just experienced this as well. Downgrading to 2.8.1 and refreshing browser cache returned it to functionality.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@jc21 commented on GitHub (Jul 13, 2021):

This is not specific to 2.9.4. This issue pops up from time to time with some users. Forcibly clearing your browser cache has been known to fix this and the root cause of the problem is still unknown.

Personally I've never had this happen to me, I pull and run each release on my own production servers and don't encounter a caching problem.

It might be helpful if users would report their browser and version, in case this applies to something non-mainstream.

The UI's index HTML page includes the version as a get param for assets, ie: src="/js/main.bundle.js?v=2.9.4" and this should be enough to cache bust, unless the caching mechanism is ignoring query params on urls (possible with some CDN's..). It could also be possible that the index HTML itself is cached, but then requests one of the JS files from the bundle that is not cached and causes a mismatch. But yeah this is all speculation until I can reproduce this.

<!-- gh-comment-id:879420411 --> @jc21 commented on GitHub (Jul 13, 2021): This is not specific to 2.9.4. This issue pops up from time to time with some users. Forcibly clearing your browser cache has been known to fix this and the root cause of the problem is still unknown. Personally I've never had this happen to me, I pull and run each release on my own production servers and don't encounter a caching problem. It might be helpful if users would report their browser and version, in case this applies to something non-mainstream. The UI's index HTML page includes the version as a get param for assets, ie: `src="/js/main.bundle.js?v=2.9.4"` and this should be enough to cache bust, unless the caching mechanism is ignoring query params on urls (possible with some CDN's..). It could also be possible that the index HTML itself is cached, but then requests one of the JS files from the bundle that is not cached and causes a mismatch. But yeah this is all speculation until I can reproduce this.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@TrustyTristan commented on GitHub (Jul 18, 2021):

I experienced this issue too.

Running Edge Version 91.0.864.70 (Official build) (64-bit)

Tried clearing site data via Developer console. No change.
Tested Incognito and there was no problem.

Cleared site data again and restarted Edge, still the same issue.

Going into Privacy, search and services > Clear browsing data > Cached images and files
This fixed it.

<!-- gh-comment-id:881997050 --> @TrustyTristan commented on GitHub (Jul 18, 2021): I experienced this issue too. Running Edge Version 91.0.864.70 (Official build) (64-bit) Tried clearing site data via Developer console. No change. Tested Incognito and there was no problem. Cleared site data again and restarted Edge, still the same issue. Going into Privacy, search and services > Clear browsing data > Cached images and files This fixed it.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@Ceriwaen commented on GitHub (Jul 18, 2021):

Thanks @TrustyTristan! Going into Firefox settings "Cookies and Site Data" and selecting "Clear Data" with both "Cookies and Site Data" and "Cached Web Content" also resolved this issue for me.

<!-- gh-comment-id:881999369 --> @Ceriwaen commented on GitHub (Jul 18, 2021): Thanks @TrustyTristan! Going into Firefox settings "Cookies and Site Data" and selecting "Clear Data" with both "Cookies and Site Data" and "Cached Web Content" also resolved this issue for me.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@nalybuites commented on GitHub (Jul 23, 2021):

I'm also having this issue. Experienced with NPM v 2.9.4 and 2.9.5 in Chrome 91.0.4472.124. Clearing cached images and files did not resolve, but downgrading to 2.8.1 did.

<!-- gh-comment-id:885433870 --> @nalybuites commented on GitHub (Jul 23, 2021): I'm also having this issue. Experienced with NPM v 2.9.4 and 2.9.5 in Chrome 91.0.4472.124. Clearing cached images and files did not resolve, but downgrading to 2.8.1 did.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@Goblin80 commented on GitHub (Jul 31, 2021):

Clearing cached images and files did trick.

chrome://settings/clearBrowserData

<!-- gh-comment-id:890361245 --> @Goblin80 commented on GitHub (Jul 31, 2021): Clearing cached images and files did trick. `chrome://settings/clearBrowserData` 

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@corbin-auriti commented on GitHub (Sep 15, 2021):

Clearing cache on Firefox worked for me thanks.

<!-- gh-comment-id:920342572 --> @corbin-auriti commented on GitHub (Sep 15, 2021): Clearing cache on Firefox worked for me thanks.

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@v3ss0n commented on GitHub (Sep 24, 2021):

Clearing cache worked for the dashboard , but when editng the host , similar problem happens

main.bundle.js?v=2.9.9:1 TypeError: Cannot read properties of undefined (reading 'extend')
    at Object.234 (11.bundle.11.js:1)
    at r (main.bundle.js?v=2.9.9:1)
    at Object.<anonymous> (11.bundle.11.js:1)
    at Object.182 (11.bundle.11.js:1)
    at r (main.bundle.js?v=2.9.9:1)
    at main.bundle.js?v=2.9.9:27
r.oe @ main.bundle.js?v=2.9.9:1
Promise.catch (async)
showNginxProxyForm @ main.bundle.js?v=2.9.9:27
click @ui.edit @ 7.bundle.7.js:1
dispatch @ main.bundle.js?v=2.9.9:27
p.handle @ main.bundle.js?v=2.9.9:27
11.bundle.11.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'extend')
    at Object.234 (11.bundle.11.js:1)
    at r (main.bundle.js?v=2.9.9:1)
    at Object.<anonymous> (11.bundle.11.js:1)
    at Object.182 (11.bundle.11.js:1)
    at r (main.bundle.js?v=2.9.9:1)
    at main.bundle.js?v=2.9.9:27
234 @ 11.bundle.11.js:1
r @ main.bundle.js?v=2.9.9:1
(anonymous) @ 11.bundle.11.js:1
182 @ 11.bundle.11.js:1
r @ main.bundle.js?v=2.9.9:1
(anonymous) @ main.bundle.js?v=2.9.9:27
Promise.catch (async)
showNginxProxyForm @ main.bundle.js?v=2.9.9:27
click @ui.edit @ 7.bundle.7.js:1
dispatch @ main.bundle.js?v=2.9.9:27
p.handle @ main.bundle.js?v=2.9.9:27
main.bundle.js?v=2.9.9:1 TypeError: n is not a constructor
    at main.bundle.js?v=2.9.9:27
    at main.bundle.js?v=2.9.9:27
r.oe @ main.bundle.js?v=2.9.9:1
Promise.catch (async)
showNginxProxyForm @ main.bundle.js?v=2.9.9:27
click @ui.edit @ 7.bundle.7.js:1
dispatch @ main.bundle.js?v=2.9.9:27
p.handle @ main.bundle.js?v=2.9.9:27
main.bundle.js?v=2.9.9:27 Uncaught (in promise) TypeError: n is not a constructor
    at main.bundle.js?v=2.9.9:27
    at main.bundle.js?v=2.9.9:27
(anonymous) @ main.bundle.js?v=2.9.9:27
(anonymous) @ main.bundle.js?v=2.9.9:27
Promise.catch (async)
showNginxProxyForm @ main.bundle.js?v=2.9.9:27
click @ui.edit @ 7.bundle.7.js:1
dispatch @ main.bundle.js?v=2.9.9:27
p.handle @ main.bundle.js?v=2.9.9:27

<!-- gh-comment-id:926908953 --> @v3ss0n commented on GitHub (Sep 24, 2021): Clearing cache worked for the dashboard , but when editng the host , similar problem happens ``` main.bundle.js?v=2.9.9:1 TypeError: Cannot read properties of undefined (reading 'extend') at Object.234 (11.bundle.11.js:1) at r (main.bundle.js?v=2.9.9:1) at Object.<anonymous> (11.bundle.11.js:1) at Object.182 (11.bundle.11.js:1) at r (main.bundle.js?v=2.9.9:1) at main.bundle.js?v=2.9.9:27 r.oe @ main.bundle.js?v=2.9.9:1 Promise.catch (async) showNginxProxyForm @ main.bundle.js?v=2.9.9:27 click @ui.edit @ 7.bundle.7.js:1 dispatch @ main.bundle.js?v=2.9.9:27 p.handle @ main.bundle.js?v=2.9.9:27 11.bundle.11.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'extend') at Object.234 (11.bundle.11.js:1) at r (main.bundle.js?v=2.9.9:1) at Object.<anonymous> (11.bundle.11.js:1) at Object.182 (11.bundle.11.js:1) at r (main.bundle.js?v=2.9.9:1) at main.bundle.js?v=2.9.9:27 234 @ 11.bundle.11.js:1 r @ main.bundle.js?v=2.9.9:1 (anonymous) @ 11.bundle.11.js:1 182 @ 11.bundle.11.js:1 r @ main.bundle.js?v=2.9.9:1 (anonymous) @ main.bundle.js?v=2.9.9:27 Promise.catch (async) showNginxProxyForm @ main.bundle.js?v=2.9.9:27 click @ui.edit @ 7.bundle.7.js:1 dispatch @ main.bundle.js?v=2.9.9:27 p.handle @ main.bundle.js?v=2.9.9:27 main.bundle.js?v=2.9.9:1 TypeError: n is not a constructor at main.bundle.js?v=2.9.9:27 at main.bundle.js?v=2.9.9:27 r.oe @ main.bundle.js?v=2.9.9:1 Promise.catch (async) showNginxProxyForm @ main.bundle.js?v=2.9.9:27 click @ui.edit @ 7.bundle.7.js:1 dispatch @ main.bundle.js?v=2.9.9:27 p.handle @ main.bundle.js?v=2.9.9:27 main.bundle.js?v=2.9.9:27 Uncaught (in promise) TypeError: n is not a constructor at main.bundle.js?v=2.9.9:27 at main.bundle.js?v=2.9.9:27 (anonymous) @ main.bundle.js?v=2.9.9:27 (anonymous) @ main.bundle.js?v=2.9.9:27 Promise.catch (async) showNginxProxyForm @ main.bundle.js?v=2.9.9:27 click @ui.edit @ 7.bundle.7.js:1 dispatch @ main.bundle.js?v=2.9.9:27 p.handle @ main.bundle.js?v=2.9.9:27 ```

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 8, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1984906359 --> @github-actions[bot] commented on GitHub (Mar 8, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@nickmartin1ee7 commented on GitHub (Feb 26, 2025):

I'm still getting this when I click on Add SSL Certificate

Image: jc21/nginx-proxy-manager:latest@sha256:02c15b64d464491d09e6d04959f26689d31aec1e02236a1675c1b85d6942c103

<!-- gh-comment-id:2683741384 --> @nickmartin1ee7 commented on GitHub (Feb 26, 2025): I'm still getting this when I click on Add SSL Certificate Image: jc21/nginx-proxy-manager:latest@sha256:02c15b64d464491d09e6d04959f26689d31aec1e02236a1675c1b85d6942c103 

kerem commented 2026-02-26 06:35:21 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 10, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3509151079 --> @github-actions[bot] commented on GitHub (Nov 10, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

dependabot/npm_and_yarn/backend/liquidjs-10.25.7

dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987

dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41

dependabot/npm_and_yarn/backend/basic-ftp-5.3.0

dependabot/npm_and_yarn/test/follow-redirects-1.16.0

dependabot/npm_and_yarn/test/axios-1.15.0

dependabot/npm_and_yarn/frontend/lodash-4.18.1

dependabot/npm_and_yarn/backend/lodash-4.18.1

dependabot/npm_and_yarn/test/lodash-4.18.1

dependabot/npm_and_yarn/frontend/vite-7.3.2

dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21

dependabot/npm_and_yarn/frontend/lodash-es-4.18.1

dependabot/npm_and_yarn/frontend/happy-dom-20.8.9

dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0

dependabot/npm_and_yarn/frontend/picomatch-4.0.4

dependabot/npm_and_yarn/backend/picomatch-2.3.2

dependabot/npm_and_yarn/frontend/yaml-1.10.3

dependabot/npm_and_yarn/test/flatted-3.4.2

dependabot/npm_and_yarn/test/tar-7.5.11

dependabot/npm_and_yarn/frontend/immutable-5.1.5

master

dependabot/npm_and_yarn/test/glob-10.5.0

dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1

dependabot/npm_and_yarn/test/form-data-4.0.4

v3-abandoned

bump-freedns

openidc

ssl-passthrough-hosts

static-content

v2.14.0

v2.13.7

v2.13.6

v2.13.5

v2.13.4

v2.13.3

v2.13.2

v2.13.1

v2.13.0

v2.12.6

v2.12.5

v2.12.4

v2.12.3

v2.12.2

v2.12.1

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.4

v2.10.3

v2.10.2

v2.10.1

v2.10.0

v2.9.22

v2.9.21

v2.9.20

v2.9.19

v2.9.18

v2.9.17

v2.9.16

v2.9.15

v2.9.14

v2.9.13

v2.9.12

v2.9.11

v2.9.10

v2.9.9

v2.9.8

v2.9.7

v2.9.6

v2.9.5

v2.9.4

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.1

v2.8.0

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.4

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.1

v2.1.0

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.0

v2.0.0

1.1.2

1.1.1

1.0.1

Labels

Clear 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

Mirrored from GitHub Pull Request

  

question

  

stale

  

troll

  

upstream issue

  

v2

  

v2

  

v2

  

v3

  

wontfix

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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#993

No description provided.