[GH-ISSUE #5115] Need restart container after add proxy host #3114

Open
opened 2026-02-26 07:37:53 +03:00 by kerem · 1 comment
Owner

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

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

Describe the bug

After updating from the old UI to the new UI, there is a problem when adding a Proxy Host. When I add a new Proxy Host, but the Proxy Host only shows the congratulations page.

The Proxy Host only starts working after I manually restart the container.

In the logs, I can see a message saying "reloading nginx", but it looks like nginx is not actually being reloaded.

Nginx Proxy Manager Version

v2.13.5

To Reproduce

Steps to reproduce the behavior:

  1. Open the new UI.
  2. Go to Proxy Hosts.
  3. Click Add Proxy Host.
  4. Fill in the required fields and save.
  5. Try accessing the newly created Proxy Host, shows the Congratulations page.
  6. The Proxy Host does not work until the container is restarted.

Expected behavior

After adding a new Proxy Host, nginx should automatically reload and the Proxy Host should work immediately without requiring a container restart.

Additional context

  • This issue occurs after upgrading from the old UI to the new UI.
  • Logs show a message like "reloading nginx", but nginx does not appear to actually reload.
  • Restarting the container manually resolves the issue.
  • Using postgres database
Originally created by @newarifrh on GitHub (Jan 1, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5115 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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 **Describe the bug** <!-- A clear and concise description of what the bug is. --> After updating from the old UI to the new UI, there is a problem when adding a Proxy Host. When I add a new Proxy Host, but the Proxy Host only shows the congratulations page. The Proxy Host only starts working after I manually restart the container. In the logs, I can see a message saying "reloading nginx", but it looks like nginx is not actually being reloaded. **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.13.5 ## To Reproduce Steps to reproduce the behavior: 1. Open the new UI. 2. Go to **Proxy Hosts**. 3. Click **Add Proxy Host**. 4. Fill in the required fields and save. 5. Try accessing the newly created Proxy Host, shows the **Congratulations** page. 6. The Proxy Host does not work until the container is restarted. ## Expected behavior After adding a new Proxy Host, nginx should automatically reload and the Proxy Host should work immediately without requiring a container restart. ## Additional context - This issue occurs after upgrading from the old UI to the new UI. - Logs show a message like **"reloading nginx"**, but nginx does not appear to actually reload. - Restarting the container manually resolves the issue. - Using postgres database
Author
Owner

@Hultzilla commented on GitHub (Jan 26, 2026):

I have the same issue, tried to just reload nginx, but the only thing that works is manually restarting the container.

<!-- gh-comment-id:3799304700 --> @Hultzilla commented on GitHub (Jan 26, 2026): I have the same issue, tried to just reload nginx, but the only thing that works is manually restarting the container.
Sign in to join this conversation.
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#3114
No description provided.