jlesage / docker-nginx-proxy-manager

Docker container for Nginx Proxy Manager
MIT License
756 stars 166 forks source link

Existing host and new host offline #287

Closed MikaelFerland closed 1 year ago

MikaelFerland commented 1 year ago

I'm using the latest docker image (23.03.2)

When I'm saving a existing host and creating a host they go offilne. I look at the /var/log/nginx/error.log and I saw this:

2023/03/17 16:16:49 [emerg] 24122#24122: unexpected ";" in /data/nginx/proxy_host/10.conf:72
2023/03/17 16:21:25 [emerg] 24142#24142: unexpected ";" in /data/nginx/proxy_host/10.conf:72
2023/03/17 16:21:49 [emerg] 24144#24144: unexpected ";" in /data/nginx/proxy_host/10.conf:72
2023/03/17 16:22:10 [emerg] 24146#24146: unexpected ";" in /data/nginx/proxy_host/10.conf:72
2023/03/17 16:22:31 [emerg] 24148#24148: unexpected ";" in /data/nginx/proxy_host/10.conf:72
2023/03/17 16:33:19 [emerg] 347#347: unexpected ";" in /data/nginx/proxy_host/16.conf:72
2023/03/17 16:33:20 [notice] 351#351: signal process started
2023/03/17 16:48:37 [notice] 375#375: signal process started
2023/03/17 16:48:46 [notice] 388#388: signal process started
2023/03/17 16:49:36 [emerg] 397#397: unexpected ";" in /data/nginx/proxy_host/16.conf:72
2023/03/17 16:49:38 [notice] 401#401: signal process started
[root@docker-e28585854df7:/app]# cat --number /data/nginx/proxy_host/16.conf
cat: /data/nginx/proxy_host/16.conf: No such file or directory

No sure why I'm not able to see the actual error, but I'm pretty sure that I briefly saw my access list not display well in the host .conf file.

If I try to access my other subdomains with the same access list and certs everything is working well.

MikaelFerland commented 1 year ago

Ok sorry it seems related to that https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2698