starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #2532] Proxy Returning a Dummy Certificate when adding Access List #1767

New issue

Closed

opened 2026-02-26 07:32:22 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:32:22 +03:00

Owner

Originally created by @isiko on GitHub (Jan 10, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2532

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
When adding an access list to a Proxy and try to access it afterwards, the Certificate used is a Dummy Certificate using localhost as the CA

Nginx Proxy Manager Version
2.9.19

To Reproduce
Steps to reproduce the behavior:

Create a Proxy Host with a
Create an Access List that allows you to access the Page
Add Access List to Proxy Host
Result as described above

Expected behavior
A Valid Certificate is returned and the Page can be accessed like normal

Operating System
Ubuntu 22.04.1 + Docker

Additional context
Docker-Version: 20.10.22

Originally created by @isiko on GitHub (Jan 10, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2532  **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** When adding an access list to a Proxy and try to access it afterwards, the Certificate used is a Dummy Certificate using localhost as the CA **Nginx Proxy Manager Version** 2.9.19 **To Reproduce** Steps to reproduce the behavior: 1. Create a Proxy Host with a 2. Create an Access List that allows you to access the Page 3. Add Access List to Proxy Host 4. Result as described above **Expected behavior** A Valid Certificate is returned and the Page can be accessed like normal **Operating System** Ubuntu 22.04.1 + Docker **Additional context** Docker-Version: 20.10.22

kerem

2026-02-26 07:32:22 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@santiagz commented on GitHub (Jan 10, 2023):

the same problem

@santiagz commented on GitHub (Jan 10, 2023): the same problem

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@PaddySe commented on GitHub (Jan 14, 2023):

Same for me, except this only happens when I use an access list with basic authentication. An access list with only IP restrictions works fine.

@PaddySe commented on GitHub (Jan 14, 2023): Same for me, except this only happens when I use an access list with basic authentication. An access list with only IP restrictions works fine.

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@PaddySe commented on GitHub (Jan 14, 2023):

Looks like the UI sometimes forgets to add the following two lines to the .conf file:

listen 443 ssl http2;
#listen [::]:443;

@PaddySe commented on GitHub (Jan 14, 2023): Looks like the UI sometimes forgets to add the following two lines to the .conf file: ``` listen 443 ssl http2; #listen [::]:443; ```

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@mull0r commented on GitHub (Mar 16, 2023):

I have this issue as well. Pretty annoying, as most hosts I have are using the ACL: I have to change all proxy hosts their configuration twice to get it back to working correctly. For instance: switching the redirect to http:// and then back to https:// (or the other way around) for all proxy hosts does the trick.

@mull0r commented on GitHub (Mar 16, 2023): I have this issue as well. Pretty annoying, as most hosts I have are using the ACL: I have to change all proxy hosts their configuration twice to get it back to working correctly. For instance: switching the redirect to http:// and then back to https:// (or the other way around) for all proxy hosts does the trick.

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 30, 2024):

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

@github-actions[bot] commented on GitHub (Jan 30, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 16, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 16, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:30:49 +03:00

[PR #1767] [MERGED] Bump json-schema from 0.2.5 to 0.4.0 in /docs #3485

kerem referenced this issue

2026-02-26 08:30:51 +03:00

[PR #1864] [MERGED] v2.9.16 #3497

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

No description provided.

Rows
Columns