starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1907] [Bug] "The migration directory is corrupt, the following files are missing:" when re-building the container ("Bad Gateway" at login) #1388

New issue
Closed
opened 2026-02-26 07:30:46 +03:00 by kerem · 7 comments
kerem commented 2026-02-26 07:30:46 +03:00
Owner
Copy link

Originally created by @ErikUden on GitHub (Mar 4, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1907

I am on a Raspberry Pi 4b with 4GB of RAM on Raspbian Lite (Debian) obviously with an arm processor!

Checklist

Describe the bug
image
This is what it shows on the login page when I try to login with the proper credentials.
I am using the yobasystems/alpine-mariadb:latest database.
I am getting the following error(s) when trying to build the image:

pi@Pi-Server:~/nginx $ docker-compose up
Starting nginx_db_1  ... done
Starting nginx_app_1 ... done
Attaching to nginx_db_1, nginx_app_1
db_1   | [i] mysqld already present, skipping creation
db_1   | [i] MySQL directory already present, skipping creation
db_1   | 2022-03-04 16:12:21 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Using Linux native AIO
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Uses event mutexes
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Number of pools: 1
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Using generic crc32 instructions
db_1   | 2022-03-04 16:12:21 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Completed initialization of buffer pool
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
db_1   | 2022-03-04 16:12:21 0 [Note] InnoDB: 10.4.15 started; log sequence number 8798007; transaction id 56715
db_1   | 2022-03-04 16:12:21 0 [Note] Plugin 'FEEDBACK' is disabled.
db_1   | 2022-03-04 16:12:21 0 [Note] Server socket created on IP: '::'.
db_1   | 2022-03-04 16:12:22 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
db_1   | 2022-03-04 16:12:22 0 [Warning] 'user' entry '@60a7e75e7f80' ignored in --skip-name-resolve mode.
db_1   | 2022-03-04 16:12:22 0 [Warning] 'proxies_priv' entry '@% root@60a7e75e7f80' ignored in --skip-name-resolve mode.
db_1   | 2022-03-04 16:12:22 0 [Note] Reading of all Master_info entries succeeded
db_1   | 2022-03-04 16:12:22 0 [Note] Added new Master_info '' to hash table
db_1   | 2022-03-04 16:12:22 0 [Note] /usr/bin/mysqld: ready for connections.
db_1   | Version: '10.4.15-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server
db_1   | 2022-03-04 16:12:22 0 [Note] InnoDB: Buffer pool(s) load completed at 220304 16:12:22
app_1  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
app_1  | [s6-init] ensuring user provided files have correct perms...exited 0.
app_1  | [fix-attrs.d] applying ownership & permissions fixes...
app_1  | [fix-attrs.d] done.
app_1  | [cont-init.d] executing container initialization scripts...
app_1  | [cont-init.d] 01_s6-secret-init.sh: executing...
app_1  | [cont-init.d] 01_s6-secret-init.sh: exited 0.
app_1  | [cont-init.d] done.
app_1  | [services.d] starting services
app_1  | [services.d] done.
app_1  | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
app_1  |   ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
app_1  |   ❯ /etc/nginx/conf.d/include/assets.conf
app_1  |   ❯ /etc/nginx/conf.d/include/ip_ranges.conf
app_1  |   ❯ /etc/nginx/conf.d/include/force-ssl.conf
app_1  |   ❯ /etc/nginx/conf.d/include/block-exploits.conf
app_1  |   ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
app_1  |   ❯ /etc/nginx/conf.d/include/proxy.conf
app_1  |   ❯ /etc/nginx/conf.d/include/resolvers.conf
app_1  |   ❯ /etc/nginx/conf.d/production.conf
app_1  |   ❯ /etc/nginx/conf.d/default.conf
app_1  | ❯ Enabling IPV6 in hosts: /data/nginx
app_1  |   ❯ /data/nginx/proxy_host/36.conf
app_1  |   ❯ /data/nginx/proxy_host/6.conf
app_1  |   ❯ /data/nginx/proxy_host/35.conf
app_1  |   ❯ /data/nginx/proxy_host/33.conf
app_1  |   ❯ /data/nginx/proxy_host/30.conf
app_1  |   ❯ /data/nginx/proxy_host/16.conf
app_1  |   ❯ /data/nginx/proxy_host/19.conf
app_1  |   ❯ /data/nginx/proxy_host/11.conf
app_1  |   ❯ /data/nginx/proxy_host/15.conf
app_1  |   ❯ /data/nginx/proxy_host/24.conf
app_1  |   ❯ /data/nginx/proxy_host/21.conf
app_1  |   ❯ /data/nginx/proxy_host/38.conf
app_1  |   ❯ /data/nginx/proxy_host/9.conf
app_1  |   ❯ /data/nginx/proxy_host/23.conf
app_1  |   ❯ /data/nginx/proxy_host/31.conf
app_1  |   ❯ /data/nginx/proxy_host/17.conf
app_1  |   ❯ /data/nginx/proxy_host/13.conf
app_1  |   ❯ /data/nginx/proxy_host/40.conf
app_1  |   ❯ /data/nginx/proxy_host/29.conf
app_1  |   ❯ /data/nginx/proxy_host/39.conf
app_1  |   ❯ /data/nginx/proxy_host/22.conf
app_1  |   ❯ /data/nginx/proxy_host/4.conf
app_1  |   ❯ /data/nginx/proxy_host/34.conf
app_1  |   ❯ /data/nginx/proxy_host/26.conf
app_1  |   ❯ /data/nginx/proxy_host/32.conf
app_1  |   ❯ /data/nginx/proxy_host/37.conf
app_1  |   ❯ /data/nginx/proxy_host/20.conf
app_1  |   ❯ /data/nginx/proxy_host/28.conf
app_1  |   ❯ /data/nginx/proxy_host/5.conf
app_1  |   ❯ /data/nginx/proxy_host/12.conf
app_1  |   ❯ /data/nginx/proxy_host/14.conf
app_1  |   ❯ /data/nginx/redirection_host/3.conf
app_1  |   ❯ /data/nginx/redirection_host/6.conf
app_1  |   ❯ /data/nginx/redirection_host/4.conf
app_1  |   ❯ /data/nginx/redirection_host/5.conf
app_1  |   ❯ /data/nginx/custom/http_top.conf
app_1  | sed: can't move '/data/nginx/custom/http_top.conffjcgGF' to '/data/nginx/custom/http_top.conf': Resource busy
app_1  |   ❯ /data/nginx/default_host/site.conf
app_1  | [3/4/2022] [4:12:27 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
app_1  | [3/4/2022] [4:12:27 PM] [Global   ] › ✖  error     The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js
app_1  | [3/4/2022] [4:12:28 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
app_1  | [3/4/2022] [4:12:28 PM] [Global   ] › ✖  error     The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js
app_1  | [3/4/2022] [4:12:29 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
app_1  | [3/4/2022] [4:12:29 PM] [Global   ] › ✖  error     The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js

The last error just repeats until infinity.
Although the erorr comes from the "app_1" container, so NGINX itself (which is why it is reported as "Unhealthy" when running docker ps) I still think this is an issue with the database.
I tried changing to the jc21/mariadb-aria:10.4, but that image seems to not exist, so it did not work out.

Nginx Proxy Manager Version
v2.8.1

To Reproduce
Steps to reproduce the behavior:
On the same server as the NGINX Proxy Manager is running there is also my Pi-hole. I updated the Pi-hole, this, however, deleted the edit I made which turned the admin panel to 8080 instead of 80. After the update, Nginx obviously did not function since the Pi hole was listening on port 80. I made the change in the lighttpd.conf file, restarted the Pi, and the error with NGINX occurred. I am using an NGINX service that rebuilds the container after every reboot to autostart it.

Operating System
Raspberry Pi on Raspbian Lite

Additional context
Recently updated Pi-Hole which reset the Pi-Hole to running on port 80, after undoing this (without editing anything regarding Nginx) the error occurred.

Originally created by @ErikUden on GitHub (Mar 4, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1907 I am on a Raspberry Pi 4b with 4GB of RAM on Raspbian Lite (Debian) obviously with an arm processor! **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 Here are some of the solutions I found: https://gitmotion.com/nginx-proxy-manager/667768676/bad-gateway-app-login-serious-issue This does not seem to work for me, however. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/310 The same kind of issue was discussed here too. **Describe the bug** ![image](https://user-images.githubusercontent.com/52011431/156799300-1c790b39-6073-424d-8b8f-e4585de771d3.png) This is what it shows on the login page when I try to login with the proper credentials. I am using the yobasystems/alpine-mariadb:latest database. I am getting the following error(s) when trying to build the image: ``` pi@Pi-Server:~/nginx $ docker-compose up Starting nginx_db_1 ... done Starting nginx_app_1 ... done Attaching to nginx_db_1, nginx_app_1 db_1 | [i] mysqld already present, skipping creation db_1 | [i] MySQL directory already present, skipping creation db_1 | 2022-03-04 16:12:21 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ... db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Using Linux native AIO db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Uses event mutexes db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Number of pools: 1 db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Using generic crc32 instructions db_1 | 2022-03-04 16:12:21 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts) db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Completed initialization of buffer pool db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active. db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. db_1 | 2022-03-04 16:12:21 0 [Note] InnoDB: 10.4.15 started; log sequence number 8798007; transaction id 56715 db_1 | 2022-03-04 16:12:21 0 [Note] Plugin 'FEEDBACK' is disabled. db_1 | 2022-03-04 16:12:21 0 [Note] Server socket created on IP: '::'. db_1 | 2022-03-04 16:12:22 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool db_1 | 2022-03-04 16:12:22 0 [Warning] 'user' entry '@60a7e75e7f80' ignored in --skip-name-resolve mode. db_1 | 2022-03-04 16:12:22 0 [Warning] 'proxies_priv' entry '@% root@60a7e75e7f80' ignored in --skip-name-resolve mode. db_1 | 2022-03-04 16:12:22 0 [Note] Reading of all Master_info entries succeeded db_1 | 2022-03-04 16:12:22 0 [Note] Added new Master_info '' to hash table db_1 | 2022-03-04 16:12:22 0 [Note] /usr/bin/mysqld: ready for connections. db_1 | Version: '10.4.15-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server db_1 | 2022-03-04 16:12:22 0 [Note] InnoDB: Buffer pool(s) load completed at 220304 16:12:22 app_1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0. app_1 | [s6-init] ensuring user provided files have correct perms...exited 0. app_1 | [fix-attrs.d] applying ownership & permissions fixes... app_1 | [fix-attrs.d] done. app_1 | [cont-init.d] executing container initialization scripts... app_1 | [cont-init.d] 01_s6-secret-init.sh: executing... app_1 | [cont-init.d] 01_s6-secret-init.sh: exited 0. app_1 | [cont-init.d] done. app_1 | [services.d] starting services app_1 | [services.d] done. app_1 | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d app_1 | ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf app_1 | ❯ /etc/nginx/conf.d/include/assets.conf app_1 | ❯ /etc/nginx/conf.d/include/ip_ranges.conf app_1 | ❯ /etc/nginx/conf.d/include/force-ssl.conf app_1 | ❯ /etc/nginx/conf.d/include/block-exploits.conf app_1 | ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf app_1 | ❯ /etc/nginx/conf.d/include/proxy.conf app_1 | ❯ /etc/nginx/conf.d/include/resolvers.conf app_1 | ❯ /etc/nginx/conf.d/production.conf app_1 | ❯ /etc/nginx/conf.d/default.conf app_1 | ❯ Enabling IPV6 in hosts: /data/nginx app_1 | ❯ /data/nginx/proxy_host/36.conf app_1 | ❯ /data/nginx/proxy_host/6.conf app_1 | ❯ /data/nginx/proxy_host/35.conf app_1 | ❯ /data/nginx/proxy_host/33.conf app_1 | ❯ /data/nginx/proxy_host/30.conf app_1 | ❯ /data/nginx/proxy_host/16.conf app_1 | ❯ /data/nginx/proxy_host/19.conf app_1 | ❯ /data/nginx/proxy_host/11.conf app_1 | ❯ /data/nginx/proxy_host/15.conf app_1 | ❯ /data/nginx/proxy_host/24.conf app_1 | ❯ /data/nginx/proxy_host/21.conf app_1 | ❯ /data/nginx/proxy_host/38.conf app_1 | ❯ /data/nginx/proxy_host/9.conf app_1 | ❯ /data/nginx/proxy_host/23.conf app_1 | ❯ /data/nginx/proxy_host/31.conf app_1 | ❯ /data/nginx/proxy_host/17.conf app_1 | ❯ /data/nginx/proxy_host/13.conf app_1 | ❯ /data/nginx/proxy_host/40.conf app_1 | ❯ /data/nginx/proxy_host/29.conf app_1 | ❯ /data/nginx/proxy_host/39.conf app_1 | ❯ /data/nginx/proxy_host/22.conf app_1 | ❯ /data/nginx/proxy_host/4.conf app_1 | ❯ /data/nginx/proxy_host/34.conf app_1 | ❯ /data/nginx/proxy_host/26.conf app_1 | ❯ /data/nginx/proxy_host/32.conf app_1 | ❯ /data/nginx/proxy_host/37.conf app_1 | ❯ /data/nginx/proxy_host/20.conf app_1 | ❯ /data/nginx/proxy_host/28.conf app_1 | ❯ /data/nginx/proxy_host/5.conf app_1 | ❯ /data/nginx/proxy_host/12.conf app_1 | ❯ /data/nginx/proxy_host/14.conf app_1 | ❯ /data/nginx/redirection_host/3.conf app_1 | ❯ /data/nginx/redirection_host/6.conf app_1 | ❯ /data/nginx/redirection_host/4.conf app_1 | ❯ /data/nginx/redirection_host/5.conf app_1 | ❯ /data/nginx/custom/http_top.conf app_1 | sed: can't move '/data/nginx/custom/http_top.conffjcgGF' to '/data/nginx/custom/http_top.conf': Resource busy app_1 | ❯ /data/nginx/default_host/site.conf app_1 | [3/4/2022] [4:12:27 PM] [Migrate ] › ℹ info Current database version: 20211108145214 app_1 | [3/4/2022] [4:12:27 PM] [Global ] › ✖ error The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js app_1 | [3/4/2022] [4:12:28 PM] [Migrate ] › ℹ info Current database version: 20211108145214 app_1 | [3/4/2022] [4:12:28 PM] [Global ] › ✖ error The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js app_1 | [3/4/2022] [4:12:29 PM] [Migrate ] › ℹ info Current database version: 20211108145214 app_1 | [3/4/2022] [4:12:29 PM] [Global ] › ✖ error The migration directory is corrupt, the following files are missing: 20210423103500_stream_domain.js, 20211108145214_regenerate_default_host.js ``` The last error just repeats until infinity. Although the erorr comes from the "app_1" container, so NGINX itself (which is why it is reported as "Unhealthy" when running docker ps) I still think this is an issue with the database. I tried changing to the jc21/mariadb-aria:10.4, but that image seems to not exist, so it did not work out. **Nginx Proxy Manager Version** v2.8.1 **To Reproduce** Steps to reproduce the behavior: On the same server as the NGINX Proxy Manager is running there is also my Pi-hole. I updated the Pi-hole, this, however, deleted the edit I made which turned the admin panel to 8080 instead of 80. After the update, Nginx obviously did not function since the Pi hole was listening on port 80. I made the change in the lighttpd.conf file, restarted the Pi, and the error with NGINX occurred. I am using an NGINX service that rebuilds the container after every reboot to autostart it. **Operating System** Raspberry Pi on Raspbian Lite **Additional context** Recently updated Pi-Hole which reset the Pi-Hole to running on port 80, after undoing this (_without editing anything regarding Nginx_) the error occurred.
kerem 2026-02-26 07:30:46 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@ErikUden commented on GitHub (Mar 4, 2022):

My config.json has private and public keys beyond the standard config, just wanted to add this as a note.

The NGINX Service itself seems to fully function, however, I simply cannot login. Hence I believe this may be a database error.

<!-- gh-comment-id:1059315678 --> @ErikUden commented on GitHub (Mar 4, 2022): My config.json has private and public keys beyond the standard config, just wanted to add this as a note. The NGINX Service itself seems to fully function, however, I simply cannot login. Hence I believe this may be a database error.
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@texneus commented on GitHub (Mar 8, 2022):

Same problem here, also on a Pi 4b with Raspian and docker, but just using the docker command line. NginxPM seems to be running and proxying, but I am unable to login. "Bad Gateway" as shown above. Version 2.9.16. Unsure of when this started.

docker create \
                  --name nginxpm \
                  --restart on-failure:5 \
                  -e DISABLE_IPV6="true" \
                  -p 80:80 \
                  -p 81:81 \
                  -p 443:443 \
                  -v /opt/nginxpm/data/nginxpm:/data \
                  -v /opt/nginxpm/data/letsencrypt:/etc/letsencrypt \
                  jc21/nginx-proxy-manager
<!-- gh-comment-id:1061377128 --> @texneus commented on GitHub (Mar 8, 2022): Same problem here, also on a Pi 4b with Raspian and docker, but just using the docker command line. NginxPM seems to be running and proxying, but I am unable to login. "Bad Gateway" as shown above. Version 2.9.16. Unsure of when this started. ``` docker create \ --name nginxpm \ --restart on-failure:5 \ -e DISABLE_IPV6="true" \ -p 80:80 \ -p 81:81 \ -p 443:443 \ -v /opt/nginxpm/data/nginxpm:/data \ -v /opt/nginxpm/data/letsencrypt:/etc/letsencrypt \ jc21/nginx-proxy-manager ```
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@ErikUden commented on GitHub (Mar 8, 2022):

Bruh

<!-- gh-comment-id:1061529451 --> @ErikUden commented on GitHub (Mar 8, 2022): Bruh
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@ErikUden commented on GitHub (Mar 12, 2022):

Any updates?

<!-- gh-comment-id:1065940931 --> @ErikUden commented on GitHub (Mar 12, 2022): Any updates?
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@ErikUden commented on GitHub (Mar 12, 2022):

I have found my error:
@texneus (maybe you have the same issue too?)
I reset my database to yobasystems' maria-db, however, that did not solve it. The issue lied within four files I had:

so nginx/data/mysql/npm
In here there there is
migrations.frm
migrations.ibd
migrations_lock.frm
migrations_lock.ibd

I replaced all of these files with a backup I made of them a while ago.
Now everything works again.
I cannot explain why, but these files got corrupted after listening on the same port as my Pi-hole. For everyone reading my solution, I hope you've made a backup, if not, try deleting these files, maybe (only after having made a backup)?

Good luck!

<!-- gh-comment-id:1065971465 --> @ErikUden commented on GitHub (Mar 12, 2022): I have found my error: @texneus (maybe you have the same issue too?) I reset my database to yobasystems' maria-db, however, that did not solve it. The issue lied within four files I had: so nginx/data/mysql/npm In here there there is migrations.frm migrations.ibd migrations_lock.frm migrations_lock.ibd I replaced all of these files with a backup I made of them a while ago. Now everything works again. I cannot explain why, but these files got corrupted after listening on the same port as my Pi-hole. For everyone reading my solution, I hope you've made a backup, if not, try deleting these files, maybe (only after having made a backup)? Good luck!
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@Buronn commented on GitHub (May 14, 2025):

I found this file, I put it in the migrations folder and it works.

https://github.com/NginxProxyManager/nginx-proxy-manager/tree/develop/backend/migrations

Im not sure if it's ok or secure to do this.

<!-- gh-comment-id:2881719903 --> @Buronn commented on GitHub (May 14, 2025): I found this file, I put it in the migrations folder and it works. https://github.com/NginxProxyManager/nginx-proxy-manager/tree/develop/backend/migrations Im not sure if it's ok or secure to do this.
kerem commented 2026-02-26 07:30:47 +03:00
Author
Owner
Copy link

@egzumer commented on GitHub (Aug 18, 2025):

I found this file, I put it in the migrations folder and it works.

What is the migration folder path?

<!-- gh-comment-id:3196055100 --> @egzumer commented on GitHub (Aug 18, 2025): > I found this file, I put it in the migrations folder and it works. What is the migration folder path?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1388
No description provided.