starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2348] Permission denied error - no access over fqdn #1665

New issue

Closed

opened 2026-02-26 07:31:57 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:31:57 +03:00

Owner

Originally created by @STR3IKERKRYPTON on GitHub (Oct 28, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2348

I'm using the latest version of the nginx proxy manager in my docker environment. Everything worked fine but recently I have the following problems in the docker logs: Permission Denied

If I access the container over the public IP:Port everything works fine. But if I use the fqdn I get after 10 secounds a gateway time-out.
However, I don't have this problem with every container. Only with the one I created last.

Could the "permission" error be the problem?

Originally created by @STR3IKERKRYPTON on GitHub (Oct 28, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2348 I'm using the latest version of the nginx proxy manager in my docker environment. Everything worked fine but recently I have the following problems in the docker logs: [Permission Denied](https://pastebin.com/yTD0Gwhw) If I access the container over the public IP:Port everything works fine. But if I use the fqdn I get after 10 secounds a gateway time-out. However, I don't have this problem with every container. Only with the one I created last. Could the "permission" error be the problem?

kerem

2026-02-26 07:31:57 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:31:58 +03:00

Author

Owner

@the1ts commented on GitHub (Oct 31, 2022):

Yes, its because of the permission problems, the reload has failed to load npm-6 which I guess is your latest one. I'm guessing the problem comes from permissions around the /data volume for NPM. I've never seen NPM itself create bad permissions, its usually how the /data/ volume is being stored.

@the1ts commented on GitHub (Oct 31, 2022): Yes, its because of the permission problems, the reload has failed to load npm-6 which I guess is your latest one. I'm guessing the problem comes from permissions around the /data volume for NPM. I've never seen NPM itself create bad permissions, its usually how the /data/ volume is being stored.

kerem commented

2026-02-26 07:31:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 6, 2024):

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

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

kerem commented

2026-02-26 07:31:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 23, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 23, 2025): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns