[GH-ISSUE #470] Broken SSL cert after proxied host update, works after disable/enable host in NginxProxyManager #396

Closed
opened 2026-02-26 06:32:41 +03:00 by kerem · 2 comments
Owner

Originally created by @spiffzilla on GitHub (Jun 23, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/470

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    Yes, sort of... newest in Unraid
  • Are you sure you're not using someone else's docker image?
    Yes
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
    Yes

Describe the bug

  • A clear and concise description of what the bug is.
    See below
  • What version of Nginx Proxy Manager is reported on the login page?
    2.2.4 (from Unraid repo)

To Reproduce
Steps to reproduce the behavior:

  1. I have Gitea installed works fine with domain name, gitea.tld.com SSL cert is working fine
  2. Update Gitea docker container via Unraid
  3. I get the SSL error
    Your connection is not private
    Attackers might be trying to steal your information from gitea.tld.com (for example, passwords,
    messages, or credit cards). Learn more
    NET::ERR_CERT_AUTHORITY_INVALID
    4, In NiginxProxyManager I disable the Gitea host
  4. In NiginxProxyManager I enable the Gitea host
  5. The SSLcertificate works agaion

NginxProxyManager is set up with an access list, only allowing LAN users
When I connect after the disable/enable i need to enter creds matching the access list

All is done on the local network....
Expected behavior
Should just work even after a container update

Operating System

  • Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error.
    Unraid
Originally created by @spiffzilla on GitHub (Jun 23, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/470 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? Yes, sort of... newest in Unraid - Are you sure you're not using someone else's docker image? Yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Yes **Describe the bug** - A clear and concise description of what the bug is. See below - What version of Nginx Proxy Manager is reported on the login page? 2.2.4 (from Unraid repo) **To Reproduce** Steps to reproduce the behavior: 1. I have Gitea installed works fine with domain name, gitea.tld.com SSL cert is working fine 2. Update Gitea docker container via Unraid 3. I get the SSL error Your connection is not private Attackers might be trying to steal your information from gitea.tld.com (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID 4, In NiginxProxyManager I disable the Gitea host 5. In NiginxProxyManager I enable the Gitea host 6. The SSLcertificate works agaion NginxProxyManager is set up with an access list, only allowing LAN users When I connect after the disable/enable i need to enter creds matching the access list All is done on the local network.... **Expected behavior** Should just work even after a container update **Operating System** - Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. Unraid
kerem 2026-02-26 06:32:41 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@spiffzilla commented on GitHub (Jun 23, 2020):

I just noticed that it's not the "original", but I might need explanation anyway if possible.

My version is:
Author: jlesage
DockerHub: jlesage/nginx-proxy-manager
Repository: Djoss' Repository Maintainer Profile
Categories: Network:Web, Network:Proxy, Tools:Utilities
DockerHub Stars: 46
Added to CA: December 19, 2018
Total Downloads: More than 5,000,000
30 Day Trend: Ranked #137 Trending
(As of June 12, 2020 9:08 pm)

<!-- gh-comment-id:648087097 --> @spiffzilla commented on GitHub (Jun 23, 2020): I just noticed that it's not the "original", but I might need explanation anyway if possible. My version is: Author: jlesage DockerHub: jlesage/nginx-proxy-manager Repository: Djoss' Repository Maintainer Profile Categories: Network:Web, Network:Proxy, Tools:Utilities DockerHub Stars: 46 Added to CA: December 19, 2018 Total Downloads: More than 5,000,000 30 Day Trend: Ranked #137 Trending (As of June 12, 2020 9:08 pm)
Author
Owner

@chaptergy commented on GitHub (May 12, 2021):

As this is fairly old I will close this issue for now. If you are still experiencing the issue, please let me know, I could reopen the issue. But you should include more information, e.g. the error log at /data/logs/error.log

<!-- gh-comment-id:839793199 --> @chaptergy commented on GitHub (May 12, 2021): As this is fairly old I will close this issue for now. If you are still experiencing the issue, please let me know, I could reopen the issue. But you should include more information, e.g. the error log at `/data/logs/error.log`
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#396
No description provided.