[GH-ISSUE #90] [Feature Request] Export Settings

kerem commented

2026-02-26 05:34:13 +03:00

Owner

Originally created by @danmed on GitHub (Mar 1, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/90

I have this up and running finally using the mariadb as part of the stack, but i'd like to move it to my external MySQL server.. Unfortunately that means (as far as i can tell) i'm going to have to add all my hosts again... (i think).

Is there any way to export the current config, rebuild the docker, and import it again once it's pointing at MySQL instead?

Originally created by @danmed on GitHub (Mar 1, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/90 I have this up and running finally using the mariadb as part of the stack, but i'd like to move it to my external MySQL server.. Unfortunately that means (as far as i can tell) i'm going to have to add all my hosts again... (i think). Is there any way to export the current config, rebuild the docker, and import it again once it's pointing at MySQL instead?

kerem closed this issue

2026-02-26 05:34:13 +03:00

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@jc21 commented on GitHub (Mar 3, 2019):

EDIT: See https://github.com/jc21/nginx-proxy-manager/discussions/1529 for information about how to export / import / migrate data from your npm instances.

Sure I can see how an export feature might be useful. For now though, you only need to keep your config file, data folder, letsencrypt folder and dump your sql.

You can export your database with a script like this:

MYSQL_USER=npm
MYSQL_PASS=npm
MYSQL_DB=npm
docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS $MYSQL_DB > dump.sql

For the rest of the data I guess it depends on how you're running the docker environment.

@jc21 commented on GitHub (Mar 3, 2019): EDIT: See https://github.com/jc21/nginx-proxy-manager/discussions/1529 for information about how to export / import / migrate data from your npm instances. Sure I can see how an export feature might be useful. For now though, you only need to keep your config file, `data` folder, `letsencrypt` folder and dump your sql. You can export your database with a script like this: ```bash MYSQL_USER=npm MYSQL_PASS=npm MYSQL_DB=npm docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS $MYSQL_DB > dump.sql ``` For the rest of the data I guess it depends on how you're running the docker environment.

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

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

when I try to import the exported data on a new created docker image, all information are back. I can see all the configuration within the UI. But it isn't working. I have to edit each proxy configuration and save it (without modification) and now it works. Is there any script for reinitializing the configuration?

@MartinKuhl commented on GitHub (May 8, 2020): when I try to import the exported data on a new created docker image, all information are back. I can see all the configuration within the UI. But it isn't working. I have to edit each proxy configuration and save it (without modification) and now it works. Is there any script for reinitializing the configuration?

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@danmed commented on GitHub (May 9, 2020):

Did you reimport the database?

@danmed commented on GitHub (May 9, 2020): Did you reimport the database?

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

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

yes I did.

@MartinKuhl commented on GitHub (May 9, 2020): yes I did.

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

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

The missing key was the folder /data/nginx. 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): The missing key was the folder /data/nginx. After saving and restoring the folder /data/nginx together with a database dump and restore now everting is back and ready to work.

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@johncadengo commented on GitHub (Dec 12, 2020):

Just for anyone else attempting this, I had a little trouble running the command as is:

docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS $MYSQL_DB > dump.sql

Because it would default to localhost for the hostname. I would get this error:

$ cat dump.sql 
mysqldump: Got error: 1045: "Access denied for user 'npm'@'localhost' (using password: YES)" when trying to connect

Not sure why, but I had to supply the hostname as 127.0.0.1 to get mine to work:

docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS -h 127.0.0.1 $MYSQL_DB > dump.sql

@johncadengo commented on GitHub (Dec 12, 2020): Just for anyone else attempting this, I had a little trouble running the command as is: ``` docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS $MYSQL_DB > dump.sql ``` Because it would default to `localhost` for the hostname. I would get this error: ``` $ cat dump.sql mysqldump: Got error: 1045: "Access denied for user 'npm'@'localhost' (using password: YES)" when trying to connect ``` Not sure why, but I had to supply the hostname as `127.0.0.1` to get mine to work: ``` docker exec -ti nginx-proxy-manager_db_1 mysqldump -u $MYSQL_USER --password=$MYSQL_PASS -h 127.0.0.1 $MYSQL_DB > dump.sql ```

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@rtthane commented on GitHub (Apr 18, 2021):

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

Can i ask what restore command you used please?

@rtthane commented on GitHub (Apr 18, 2021): > The missing key was the folder /data/nginx. After saving and restoring the folder /data/nginx together with a database dump and restore now everting is back and ready to work. Can i ask what restore command you used please?

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@MartinKuhl commented on GitHub (Apr 19, 2021):

Hi @rtthane,
first I save the following folders:

docker exec -it nginx tar -zcvf /transfer/backup/nginx/SSL_backup.tar.gz /etc/letsencrypt/
docker exec -it nginx tar -zcvf /transfer/backup/nginx/nginx_conf.tar.gz /data/nginx

and the DB (remember to replace mysqluser and mysqlpassword with the values from your docker-compose):

docker exec -it db bash -c "mysqldump --user=mysqluser --password=mysqlpassword nginx > /transfer/backup/nginx/nginx-backup.sql"

For the restore I use the following commands (replace username and password again):

docker exec -it db bash -c "mysqldump --user=mysqluser --password=mysqlpassword nginx > /transfer/backup/nginx/nginx-backup.sql"
docker-compose restart nginx
docker exec -it nginx nginx -t
docker exec -it nginx nginx -s reload

@MartinKuhl commented on GitHub (Apr 19, 2021): Hi @rtthane, first I save the following folders: ``` docker exec -it nginx tar -zcvf /transfer/backup/nginx/SSL_backup.tar.gz /etc/letsencrypt/ docker exec -it nginx tar -zcvf /transfer/backup/nginx/nginx_conf.tar.gz /data/nginx ``` and the DB (remember to replace `mysqluser` and `mysqlpassword` with the values from your docker-compose): ``` docker exec -it db bash -c "mysqldump --user=mysqluser --password=mysqlpassword nginx > /transfer/backup/nginx/nginx-backup.sql" ``` For the restore I use the following commands (replace username and password again): ``` docker exec -it db bash -c "mysqldump --user=mysqluser --password=mysqlpassword nginx > /transfer/backup/nginx/nginx-backup.sql" docker-compose restart nginx docker exec -it nginx nginx -t docker exec -it nginx nginx -s reload ```

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@rtthane commented on GitHub (Apr 19, 2021):

Hi @rtthane,
first I save the following folders:
docker exec -it nginx tar -zcvf /transfer/backup/nginx/SSL_backup.tar.gz /etc/letsencrypt/
docker exec -it nginx tar -zcvf /transfer/backup/nginx/nginx_conf.tar.gz /data/nginx

and the DB:
docker exec -it db bash -c "mysqldump -uadmin -p123456 nginx > /transfer/backup/nginx/nginx-backup.sql"

For the restore I use the following commands:

docker exec -it db bash -c "mysqldump -uadmin -p123456 nginx > /transfer/backup/nginx/nginx-backup.sql"
docker-compose restart nginx
docker exec -it nginx nginx -t
docker exec -it nginx nginx -s reload

@MartinKuhl really useful info, thanks for taking the time to post it.

@rtthane commented on GitHub (Apr 19, 2021): > Hi @rtthane, > first I save the following folders: > docker exec -it nginx tar -zcvf /transfer/backup/nginx/SSL_backup.tar.gz /etc/letsencrypt/ > docker exec -it nginx tar -zcvf /transfer/backup/nginx/nginx_conf.tar.gz /data/nginx > > and the DB: > docker exec -it db bash -c "mysqldump -uadmin -p123456 nginx > /transfer/backup/nginx/nginx-backup.sql" > > For the restore I use the following commands: > > docker exec -it db bash -c "mysqldump -uadmin -p123456 nginx > /transfer/backup/nginx/nginx-backup.sql" > docker-compose restart nginx > docker exec -it nginx nginx -t > docker exec -it nginx nginx -s reload @MartinKuhl really useful info, thanks for taking the time to post it.

kerem commented

2026-02-26 05:34:14 +03:00

Author

Owner

@chaptergy commented on GitHub (May 10, 2021):

Closing this in favor of https://github.com/jc21/nginx-proxy-manager/issues/168

@chaptergy commented on GitHub (May 10, 2021): Closing this in favor of https://github.com/jc21/nginx-proxy-manager/issues/168

Rows
Columns

[GH-ISSUE #90] [Feature Request] Export Settings #81