mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #119] Ngix fail to start #107
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @frozenstitches on GitHub (Apr 17, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/119
My log is being filled up with:
[nginx] starting...
nginx: [emerg] unknown directive "null" in /data/nginx/proxy_host/7.conf:30
I’m on a docker in unraid
@jc21 commented on GitHub (Apr 17, 2019):
can you tell me what's on that line in that file? It will be in your mounted data folder
@frozenstitches commented on GitHub (Apr 18, 2019):
location / {# Access List
In the file it refers to Lidarr. The certificate is about to expire and I’m not sure if it renewed. Also I have it temporarily disabled in the panel and that docker is not currently installed.
@jc21 commented on GitHub (Apr 18, 2019):
That's the entire file contents? seems to be a lot missing.
Any letsencrypt certs will not be able to renew when nginx is down altogether. If they expire and you're not using them, no big deal, they can renew later when nginx is back up.
@frozenstitches commented on GitHub (Apr 18, 2019):
------------------------------------------------$# Lidarr.example.net
------------------------------------------------$
server {
��set $forward_scheme https;
��set $server���������"192.168.1.87";
��set $port�����������8686;
��listen 8080;
��server_name Lidarr.example.net;
�����������������[ Read 45 lines ]
I edited out my domain with example.net
@frozenstitches commented on GitHub (Apr 19, 2019):
I ended up deleting the entry in the proxy host webui and every thing is back up and running.
@jc21 commented on GitHub (Apr 23, 2019):
Definitely seems weird. Re-open this if it happens again.