Need restart container after add proxy host

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

Reproduce the issue on Nginx Proxy Manager v2.13.5 using the new UI and a PostgreSQL database, then trace the path triggered when saving a Proxy Host and the reported “reloading nginx” operation. Compare it with a manual container restart; done means a newly saved Proxy Host works immediately without restarting the container.