[GH-ISSUE #1898] Some SSL settings are not saved #1382

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

Originally created by @CWempe on GitHub (Feb 27, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1898

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
After setting up a new host with lets encrypt, the SSL settings are lost/not saved.

I noticed this behavior for all my ~12 hosts I set up in the last days.

Nginx Proxy Manager Version
v2.9.16

To Reproduce
Steps to reproduce the behavior:

  1. Create a new prxy host
  2. define new Lets Encrypt
  3. save and wait
  4. open host settings
  5. see the settings being resetted

Expected behavior
settings should still be active

Screenshots
image

image

open again and settings are lost:

image

Operating System
Debian

Additional context

Originally created by @CWempe on GitHub (Feb 27, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1898 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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** After setting up a new host with lets encrypt, the SSL settings are lost/not saved. I noticed this behavior for all my ~12 hosts I set up in the last days. **Nginx Proxy Manager Version** v2.9.16 **To Reproduce** Steps to reproduce the behavior: 1. Create a new prxy host 2. define new Lets Encrypt 3. save and wait 4. open host settings 5. see the settings being resetted **Expected behavior** settings should still be active **Screenshots** ![image](https://user-images.githubusercontent.com/1270359/155891524-14bdf912-8c73-474f-aae8-bb1ce1649e0c.png) ![image](https://user-images.githubusercontent.com/1270359/155891528-153006d9-1eb0-46a9-ad89-d57de9d148f5.png) open again and settings are lost: ![image](https://user-images.githubusercontent.com/1270359/155891539-f7f96819-b996-4bca-9f6f-3dafac415d96.png) **Operating System** Debian **Additional context**
kerem 2026-02-26 07:30:45 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@CWempe commented on GitHub (Feb 27, 2022):

Could be related to https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1753?!

<!-- gh-comment-id:1053614744 --> @CWempe commented on GitHub (Feb 27, 2022): Could be related to https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1753?!
Author
Owner

@github-actions[bot] commented on GitHub (Feb 22, 2024):

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

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

@github-actions[bot] commented on GitHub (Apr 7, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2781853591 --> @github-actions[bot] commented on GitHub (Apr 7, 2025): Issue was closed due to inactivity.
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#1382
No description provided.