starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #399] No loading of configuration after reimport of SQL dump #339

New issue

Closed

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

kerem commented

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

Owner

Originally created by @MartinKuhl on GitHub (May 7, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/399

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? -> xes
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

after a restore of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a configuration an simply save it without any edit and now the SSL configuration is working.

To Reproduce
Steps to reproduce the behavior:
after a restore (docker exec -it db bash -c "mysql -uXXX -pYYYY nginx < /var/www/html/interface/nginx/nginx-backup.sql") of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a proxy host configuration and simply save it without any edit and now the SSL configuration is working.
Without these "edit" I get a NET::ERR_CERT_INVALID error message.
Is there any way to do these edit via script?

Expected behavior
After loading the backup everything working without editing and saving each entry of host proxy configuration.

Operating System

Docker in Mac OS (latest versions)

Additional context

Chrome and Safari

Originally created by @MartinKuhl on GitHub (May 7, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/399 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? -> xes - 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** - after a restore of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a configuration an simply save it without any edit and now the SSL configuration is working. **To Reproduce** Steps to reproduce the behavior: after a restore (docker exec -it db bash -c "mysql -uXXX -pYYYY nginx < /var/www/html/interface/nginx/nginx-backup.sql") of the configuration (db entries) all SSL Certificates and Configuration is back. But it is not functional. I have to open a proxy host configuration and simply save it without any edit and now the SSL configuration is working. Without these "edit" I get a NET::ERR_CERT_INVALID error message. Is there any way to do these edit via script? **Expected behavior** After loading the backup everything working without editing and saving each entry of host proxy configuration. **Operating System** - Docker in Mac OS (latest versions) **Additional context** - Chrome and Safari

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@Indemnity83 commented on GitHub (May 11, 2020):

When you restored the SQL backup, did you also restore all the configuration files that are stored in the /data volume?

Nginx doesn't read its configurations from the database, it loads the files stored in /data. It sounds like you've restored the database but not the configuration files. Re-saving the hosts will re-generate the Nginx configs and reload Nginx so it picks up the changes.

@Indemnity83 commented on GitHub (May 11, 2020): When you restored the SQL backup, did you also restore all the configuration files that are stored in the /data volume? Nginx doesn't read its configurations from the database, it loads the files stored in /data. It sounds like you've restored the database but not the configuration files. Re-saving the hosts will re-generate the Nginx configs and reload Nginx so it picks up the changes.

kerem commented

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

Author

Owner

@MartinKuhl commented on GitHub (May 11, 2020):

That was the missing hint. After saving and restoring the folder /data/nginx together with a database dump and restore now everting is back and ready to work.

@MartinKuhl commented on GitHub (May 11, 2020): That was the missing hint. After saving and restoring the folder /data/nginx together with a database dump and restore now everting is back and ready to work.

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

No description provided.

Rows
Columns