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 #393] 500 Internal error on access lists #335

New issue

Closed

opened 2026-02-26 06:32:22 +03:00 by kerem · 11 comments

kerem commented

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

Owner

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

Latest version

Originally created by @modem7 on GitHub (May 2, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/393 ![image](https://user-images.githubusercontent.com/4349962/80892716-2de9d800-8cc4-11ea-9c9d-6738240424e7.png) Latest version

kerem

2026-02-26 06:32:22 +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 10, 2020):

Any chance of getting the java console log, network response, or docker log for this? not going to be able to do much without more information here.

@Indemnity83 commented on GitHub (May 10, 2020): Any chance of getting the java console log, network response, or docker log for this? not going to be able to do much without more information here.

kerem commented

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

Author

Owner

@modem7 commented on GitHub (May 10, 2020):

Any chance of getting the java console log, network response, or docker log for this? not going to be able to do much without more information here.

Of course!

[5/10/2020] [8:39:35 AM] [Express  ] › ⚠  warning   select `access_list_client`.* from `access_list_client` where `access_list_client`.`access_list_id` in (1, 3, 2, 4, 5) - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine 'InnoDB'


[5/10/2020] [8:39:37 AM] [Express  ] › ⚠  warning   select `access_list_client`.* from `access_list_client` where `access_list_client`.`access_list_id` in (1, 3, 2, 4, 5) - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine 'InnoDB'

Nginx Docker log:
https://pastebin.com/rhJvhKtz

Nginx DB Docker log:
https://pastebin.com/MQ1vz2eL

Docker compose:
https://pastebin.com/7Ny5fRTi

Let me know if you need the java log and network response (unsure how to get the network response in this case) on top of these.

Thanks!

@modem7 commented on GitHub (May 10, 2020): > > > Any chance of getting the java console log, network response, or docker log for this? not going to be able to do much without more information here. Of course! ``` [5/10/2020] [8:39:35 AM] [Express ] › ⚠ warning select `access_list_client`.* from `access_list_client` where `access_list_client`.`access_list_id` in (1, 3, 2, 4, 5) - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine 'InnoDB' [5/10/2020] [8:39:37 AM] [Express ] › ⚠ warning select `access_list_client`.* from `access_list_client` where `access_list_client`.`access_list_id` in (1, 3, 2, 4, 5) - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine 'InnoDB' ``` Nginx Docker log: https://pastebin.com/rhJvhKtz Nginx DB Docker log: https://pastebin.com/MQ1vz2eL Docker compose: https://pastebin.com/7Ny5fRTi Let me know if you need the java log and network response (unsure how to get the network response in this case) on top of these. Thanks!

kerem commented

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

Author

Owner

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

I notice in your compose file you have an image commented out; did you use mariadb:latest when upgrading to v2.2.3?

It may have created to access_list_client table using InnoDB. the jc21/mariadb-aria image disables InnoDB, which would cause the error you're seeing above.

Try swapping back to mariadb:latest and see if it works. I'm not sure what the ramifications are of using InnoDB here are, @jc21 would probably have to weigh in if it means you need to actually 'fix' your database or just stick with mariadb:latest.

@Indemnity83 commented on GitHub (May 11, 2020): I notice in your compose file you have an image commented out; did you use `mariadb:latest` when upgrading to v2.2.3? It may have created to access_list_client table using `InnoDB`. the `jc21/mariadb-aria` image [disables `InnoDB`](https://github.com/jc21/docker-mariadb-aria/blob/08926ef8228978c92e72edbf1c955a9647bb30dd/00_aria.cnf#L5), which would cause the error you're seeing above. Try swapping back to `mariadb:latest` and see if it works. I'm not sure what the ramifications are of using `InnoDB` here are, @jc21 would probably have to weigh in if it means you need to actually 'fix' your database or just stick with `mariadb:latest`.

kerem commented

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

Author

Owner

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

Ah no, the update was done a few months ago - I need to clean up my docker compose!

I've been on mariadb-aria since just before March. The docker-compose file (for Nginx + DB) hasn't been changed since around that time as it was working as intended (me being a dumbass should have probably put versioning instead of auto-updating to latest however)

@modem7 commented on GitHub (May 11, 2020): Ah no, the update was done a few months ago - I need to clean up my docker compose! I've been on mariadb-aria since just before March. The docker-compose file (for Nginx + DB) hasn't been changed since around that time as it was working as intended (me being a dumbass should have probably put versioning instead of auto-updating to latest however)

kerem commented

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

Author

Owner

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

It may still be that the database is set to use InnoDB as the default table storage engine.

I still think it is worth trying (after making a backup) swapping back to the mariadb:latest image for the DB. It really looks like your accees_list_clients table got built with the InnoDB engine and jc21/mariadb-aria won't be able to open it

@Indemnity83 commented on GitHub (May 11, 2020): It may still be that the database is set to use InnoDB as the default table storage engine. I still think it is worth trying (after making a backup) swapping back to the `mariadb:latest` image for the DB. It really looks like your accees_list_clients table got built with the InnoDB engine and `jc21/mariadb-aria` won't be able to open it

kerem commented

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

Author

Owner

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

ALTER TABLE accees_list_clients ENGINE=Aria;

seems like it would fix it, but I obviously have no way to test this

@Indemnity83 commented on GitHub (May 11, 2020): ```sql ALTER TABLE accees_list_clients ENGINE=Aria; ``` *seems* like it would fix it, but I obviously have no way to test this

kerem commented

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

Author

Owner

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

Ahhah - do you know if (and I'll make a backup regardless of the volume(s)) npm will re-create the database entries and populate with the data?

If not, it's no biggie, bit of a bugger but 20 minutes of work will restore the whole thing

I'll try doing the alter table and see if it resolves (gotta figure out how to first!) (after a backup)

@modem7 commented on GitHub (May 11, 2020): Ahhah - do you know if (and I'll make a backup regardless of the volume(s)) npm will re-create the database entries and populate with the data? If not, it's no biggie, bit of a bugger but 20 minutes of work will restore the whole thing I'll try doing the alter table and see if it resolves (gotta figure out how to first!) (after a backup)

kerem commented

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

Author

Owner

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

the DB container should just come up with all the data still in-tact (it's all in the /var/lib/mysql volume).

@Indemnity83 commented on GitHub (May 11, 2020): the DB container *should* just come up with all the data still in-tact (it's all in the /var/lib/mysql volume).

kerem commented

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

Author

Owner

@modem7 commented on GitHub (May 13, 2020):

Looks like switching to mariadb did the job!

Do we want to keep this open to investigate jc21/mariadb-aria or close it?

Thank you very much!

@modem7 commented on GitHub (May 13, 2020): Looks like switching to mariadb did the job! Do we want to keep this open to investigate jc21/mariadb-aria or close it? Thank you very much!

kerem commented

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

Author

Owner

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

I’m certain it’s because the DB was created in one environment then switched. Generally not a problem until a new table is added.

There may be a similar alter database command to change the default table engine too.

@Indemnity83 commented on GitHub (May 13, 2020): I’m certain it’s because the DB was created in one environment then switched. Generally not a problem until a new table is added. There may be a similar alter database command to change the default table engine too.

kerem commented

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

Author

Owner

@modem7 commented on GitHub (May 13, 2020):

For now, let's assume that your thoughts are correct on this one! I know I did recreate things, but whether I did it with the same volume or not, I cannot recall!

We'll close this for now as things are working as intended, and hopefully it won't resurface!

Thank you once again!

@modem7 commented on GitHub (May 13, 2020): For now, let's assume that your thoughts are correct on this one! I know I did recreate things, but whether I did it with the same volume or not, I cannot recall! We'll close this for now as things are working as intended, and hopefully it won't resurface! Thank you once again!

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

No description provided.

Rows
Columns