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 #5144] `aeb4424` broke my proxy manager instance (log.conf not found) #3131

New issue

Open

opened 2026-02-26 07:37:55 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:37:55 +03:00

Owner

Originally created by @WouterGritter on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5144

I assume I'm not the only one who uses their own nginx.conf, a modified version of what's shipped with nginx-proxy-manager. aeb4424 broke my instance due to referencing a log config file called log-proxy.conf instead of log.conf which my older nginx.conf still expected.

I understand that this sometimes needs to be done. But renaming a file log.conf -> log-proxy.conf seems unnecessary, and not done with the spirit of minimal change in mind.

Though I may not be running a supported use case (shipping my own nginx.conf), I think its not unreasonable to ask to keep scenarios like this in mind for future pull requests.

Originally created by @WouterGritter on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5144 I assume I'm not the only one who uses their own `nginx.conf`, a modified version of what's shipped with nginx-proxy-manager. aeb4424 broke my instance due to referencing a log config file called `log-proxy.conf` instead of `log.conf` which my older nginx.conf still expected. I understand that this sometimes _needs_ to be done. But renaming a file `log.conf` -> `log-proxy.conf` seems unnecessary, and not done with the spirit of minimal change in mind. Though I may not be running a supported use case (shipping my own `nginx.conf`), I think its not unreasonable to ask to keep scenarios like this in mind for future pull requests.

kerem commented

2026-02-26 07:37:56 +03:00

Author

Owner

@cnowacki commented on GitHub (Jan 14, 2026):

You are not the only one who uses their own nginx.conf. I ran into the same issue this morning.

@cnowacki commented on GitHub (Jan 14, 2026): You are not the only one who uses their own nginx.conf. I ran into the same issue this morning.

kerem commented

2026-02-26 07:37:56 +03:00

Author

Owner

@WouterGritter commented on GitHub (Jan 14, 2026):

Good to hear. For anyone else with the issue, the fix is to change the following line in your own nginx.conf:
include /etc/nginx/conf.d/include/log.conf
to
include /etc/nginx/conf.d/include/log-proxy.conf

I wonder if it might be beneficial to make a PR to rename this file back to log.conf?

@WouterGritter commented on GitHub (Jan 14, 2026): Good to hear. For anyone else with the issue, the fix is to change the following line in your own `nginx.conf`: `include /etc/nginx/conf.d/include/log.conf` to `include /etc/nginx/conf.d/include/log-proxy.conf` I wonder if it might be beneficial to make a PR to rename this file back to `log.conf`?

kerem commented

2026-02-26 07:37:56 +03:00

Author

Owner

@CyborgRider commented on GitHub (Jan 19, 2026):

@WouterGritter You're genuinely my hero. I have Proxmox running behind this and when this change happened, I couldn't get in to my admin portal to work on repairing this. Luckily I had a VPN from my phone to my local router, and I could access the admin portal to reload a backup.

After all that running around, I finally got the change made on my nginx.conf, then ran the script I made to shut down, pull, and restart the docker container... It only took me about 5 hours, at my office, but I finally got it up and running with the help of this comment:

For anyone else with the issue, the fix is to change the following line in your own nginx.conf: include /etc/nginx/conf.d/include/log.conf to include /etc/nginx/conf.d/include/log-proxy.conf

I wonder if it might be beneficial to make a PR to rename this file back to log.conf?

To shorten my experience to one suggestion:
IF YOU'RE GOING TO MAKE A CHANGE THAT HAS THE POTENTIAL TO TAKE DOWN SEVERAL WEBSITES WITH ONE UPDATE, PLEASE LET US KNOW WHAT TO CHANGE IN THE UPDATE NOTES BEFORE PUSHING THIS TO EVERYONE!
I don't feel like anyone should have to be going through the github change notes just to figure that the name of a single file was changed, and broke the whole app from loading. I very much appreciate your time in doing so Wouter. You've saved my @ on this fine Monday. Glad I don't have automatic updates setup.

@CyborgRider commented on GitHub (Jan 19, 2026): @WouterGritter You're genuinely my hero. I have Proxmox running behind this and when this change happened, I couldn't get in to my admin portal to work on repairing this. Luckily I had a VPN from my phone to my local router, and I could access the admin portal to reload a backup. After all that running around, I finally got the change made on my nginx.conf, then ran the script I made to shut down, pull, and restart the docker container... It only took me about 5 hours, at my office, but I finally got it up and running with the help of this comment: > For anyone else with the issue, the fix is to change the following line in your own `nginx.conf`: `include /etc/nginx/conf.d/include/log.conf` to `include /etc/nginx/conf.d/include/log-proxy.conf` > > I wonder if it might be beneficial to make a PR to rename this file back to `log.conf`? To shorten my experience to one suggestion: IF YOU'RE GOING TO MAKE A CHANGE THAT HAS THE POTENTIAL TO TAKE DOWN SEVERAL WEBSITES WITH ONE UPDATE, PLEASE LET US KNOW WHAT TO CHANGE IN THE UPDATE NOTES BEFORE PUSHING THIS TO EVERYONE! I don't feel like anyone should have to be going through the github change notes just to figure that the name of a single file was changed, and broke the whole app from loading. I very much appreciate your time in doing so Wouter. You've saved my @$$ on this fine Monday. Glad I don't have automatic updates setup.

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

No description provided.

Rows
Columns

[GH-ISSUE #5144] aeb4424 broke my proxy manager instance (log.conf not found) #3131

[GH-ISSUE #5144] `aeb4424` broke my proxy manager instance (log.conf not found) #3131