NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Deleting a access list while it´s referenced as an access list in a proxy host results in a SSL_ERROR_UNRECOGNIZED_NAME_ALERT

Open
#4,573 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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

Deleting an access list that is currently in use by a proxy host results in a corrupted or misconfigured SSL certificate. Although the proxy host appears to default back to "Publicly Accessible," the setting is not properly applied. As a result, accessing the domain leads to an SSL_ERROR_UNRECOGNIZED_NAME_ALERT. To resolve the issue, you must manually edit the proxy host and explicitly reselect "Publicly Accessible" in the Access List settings.

Nginx Proxy Manager Version

v2.12.3

To Reproduce
Steps to reproduce the behavior:
1.Create an Access List in Nginx Proxy Manager (NPM).
2. Assign that Access List to an existing Proxy Host.
3. Delete the Access List from NPM.
4. Attempt to access the domain associated with the Proxy Host.

Expected behavior

The Proxy Host should automatically fall back to "Publicly Accessible" and continue to serve the site correctly, including a valid SSL certificate. There should be no SSL error when accessing the domain.

Screenshots

Image

Operating System

I used firefox in Windows 11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Reproduce the issue using the listed steps on Nginx Proxy Manager v2.12.3, then trace how deleting an access list affects its referenced proxy host and SSL configuration. Done means the proxy host falls back to Publicly Accessible and serves the domain without an SSL_ERROR_UNRECOGNIZED_NAME_ALERT.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx, typescript
Domain
backend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.