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 #3336] Redeployment of NGINX Proxy Manager Official Docker maps incorrect data paths, resulting in theoretical data loss without intervention #2243

New issue

Closed

opened 2026-02-26 07:34:41 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:34:41 +03:00

Owner

Originally created by @defconxt on GitHub (Nov 21, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3336

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 redeployed my NGINX Proxy Manager container, upon doing so it recreated a new /data/compose/1/v2 directory unknowngly instead of using the /data/compose/1/v1 directory to retain my BIND Volume data.

The result was all of my NGINX config was blown away and no longer functioning even though the docker container was running fine.

Nginx Proxy Manager Version
2.10.4

Expected behavior
I expect the docker container to first check and map existing SQLite Database, entire data folder, and entire letsencrypt folders before arbitrarily creating a new unused directory causing unneeded confusion.

Operating System
Docker on Ubuntu 22.04 LTS

Additional context
How I fixed this and recovered my database:

Kill Docker container (NGINX Proxy Manager)
Load up WinSCP, utilize SFTP to connect to your Ubuntu base VM, then copy the entire /data/compose/1/v1 directory to my local hard drive.
Copy data + letsencrypt to the new /data/compose/1/v2 directory and overwrite everything with your old data.
Start the docker container back up, all settings are back as they should be.
Create a rsync backup to remote storage after you realize how annoying this would have been if you didn't figure out this solution and had to start from scratch.

Please fix this, this should be the default functionaity.

Originally created by @defconxt on GitHub (Nov 21, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3336 **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 redeployed my NGINX Proxy Manager container, upon doing so it recreated a new /data/compose/1/v2 directory unknowngly instead of using the /data/compose/1/v1 directory to retain my BIND Volume data. The result was all of my NGINX config was blown away and no longer functioning even though the docker container was running fine. **Nginx Proxy Manager Version** 2.10.4 **Expected behavior** I expect the docker container to first check and map existing SQLite Database, entire data folder, and entire letsencrypt folders before arbitrarily creating a new unused directory causing unneeded confusion. **Operating System** Docker on Ubuntu 22.04 LTS **Additional context** How I fixed this and recovered my database: 1. Kill Docker container (NGINX Proxy Manager) 2. Load up WinSCP, utilize SFTP to connect to your Ubuntu base VM, then copy the entire /data/compose/1/v1 directory to my local hard drive. 3. Copy data + letsencrypt to the new /data/compose/1/v2 directory and overwrite everything with your old data. 4. Start the docker container back up, all settings are back as they should be. 5. Create a rsync backup to remote storage after you realize how annoying this would have been if you didn't figure out this solution and had to start from scratch. Please fix this, this should be the default functionaity.

kerem

2026-02-26 07:34:41 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 28, 2024):

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

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

kerem commented

2026-02-26 07:34:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 30, 2025):

Issue was closed due to inactivity.

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

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

No description provided.

Rows
Columns