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 #4134] 502 Bad Gateway error in Nginx Proxy Manager with 'migrations_lock.frm' permission denied in logs #2682

New issue

Open

opened 2026-02-26 07:36:27 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 07:36:27 +03:00

Owner

Originally created by @matiasAS on GitHub (Nov 3, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4134

Hello,

Checklist
Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes, 'jc21/nginx-proxy-manager:2.12.1'
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 am experiencing a 502 Bad Gateway error in Nginx Proxy Manager when trying to access my upstream server. The upstream server is accessible directly, but when accessed through Nginx Proxy Manager, it returns a 502 error. I checked the logs in Docker (nginx-proxy-manager-app-1 container) and found the following error:

Nginx Proxy Manager Version
2.12.1

To Reproduce Steps to reproduce the behavior:

1- Configure a new proxy host in Nginx Proxy Manager with the IP and port of the upstream server.
2- Attempt to access the configured domain.
3- Observe the 502 Bad Gateway error in the browser.

Expected behavior
The upstream server should be accessible through Nginx Proxy Manager without errors.

Screenshots

Operating System
Running on Ubuntu Server 22.04 in a virtual machine.

Additional context
Docker version: 26.1.4
Browser version: 129.0.6668.58
This issue also occurred in previous versions of Nginx Proxy Manager (2.11.x) and was not resolved by updating to 2.12.1.

Best regards
Matias

Originally created by @matiasAS on GitHub (Nov 3, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4134 Hello,  **Checklist** Checklist Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? Yes, **'jc21/nginx-proxy-manager:2.12.1'** 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 am experiencing a 502 Bad Gateway error in Nginx Proxy Manager when trying to access my upstream server. The upstream server is accessible directly, but when accessed through Nginx Proxy Manager, it returns a 502 error. I checked the logs in Docker (nginx-proxy-manager-app-1 container) and found the following error: ![image](https://github.com/user-attachments/assets/8c9d1337-78c6-444a-8fc1-22bd7aad1c63) **Nginx Proxy Manager Version** 2.12.1 **To Reproduce Steps to reproduce the behavior:** 1- Configure a new proxy host in Nginx Proxy Manager with the IP and port of the upstream server. 2- Attempt to access the configured domain. 3- Observe the 502 Bad Gateway error in the browser. **Expected behavior** The upstream server should be accessible through Nginx Proxy Manager without errors. **Screenshots** ![image](https://github.com/user-attachments/assets/efb6896c-15a2-4269-9cf0-d34cb4eb8ad0) **Operating System** Running on Ubuntu Server 22.04 in a virtual machine. **Additional context** Docker version: 26.1.4 Browser version: 129.0.6668.58 This issue also occurred in previous versions of Nginx Proxy Manager (2.11.x) and was not resolved by updating to 2.12.1. Best regards Matias

kerem added the

bug

label

2026-02-26 07:36:27 +03:00

kerem commented

2026-02-26 07:36:27 +03:00

Author

Owner

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

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

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

kerem commented

2026-02-26 07:36:27 +03:00

Author

Owner

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

What does it mean that it is obsolete? Was it resolved?

@matiasAS commented on GitHub (May 14, 2025): What does it mean that it is obsolete? Was it resolved?

kerem commented

2026-02-26 07:36:28 +03:00

Author

Owner

@matiasAS commented on GitHub (May 28, 2025):

Hi, the issue is still happening on version 2.12.1.

The upstream server is accessible directly, but through Nginx Proxy Manager it returns a 502 Bad Gateway. The error in the logs shows a permission problem with migrations_lock.frm.

Please let me know if there’s any workaround or if more information is needed to debug this issue.

This issue prevents basic functionality and should not be marked as stale.

Thanks.

@matiasAS commented on GitHub (May 28, 2025): Hi, the issue is still happening on version 2.12.1. The upstream server is accessible directly, but through Nginx Proxy Manager it returns a 502 Bad Gateway. The error in the logs shows a permission problem with `migrations_lock.frm`. Please let me know if there’s any workaround or if more information is needed to debug this issue. This issue prevents basic functionality and should not be marked as stale. Thanks.

kerem commented

2026-02-26 07:36:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 11, 2026):

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

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

kerem commented

2026-02-26 07:36:28 +03:00

Author

Owner

@matiasAS commented on GitHub (Jan 11, 2026):

Was it resolved in v2.13.5?

@matiasAS commented on GitHub (Jan 11, 2026): Was it resolved in v2.13.5?

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

No description provided.

Rows
Columns