Do no use non-ASCII characters in loaded configs
I had an issue with Certbot (let's encrypt) which failed to reload nginx due to a non-ASCII character in a loaded config file. E.g.: `Attempting to renew cert (domain.com) from /etc/letsencrypt/renewal/domain.com.conf produced an unexpected error: 'ascii' codec can't decode byte 0xe2 in position 762: ordinal not in range(128). Skipping.` I found this character using `grep -r -P '[^\x00-\x7f]' /etc/nginx`.
This commit is contained in:
parent
28cb47df42
commit
d2f597235a
|
@ -14,7 +14,7 @@
|
||||||
# https://tools.ietf.org/html/rfc7034#section-2.1.
|
# https://tools.ietf.org/html/rfc7034#section-2.1.
|
||||||
#
|
#
|
||||||
# Keep in mind that while you could send the `X-Frame-Options` header for all
|
# Keep in mind that while you could send the `X-Frame-Options` header for all
|
||||||
# of your website’s pages, this has the potential downside that it forbids even
|
# of your website's pages, this has the potential downside that it forbids even
|
||||||
# non-malicious framing of your content (e.g.: when users visit your website
|
# non-malicious framing of your content (e.g.: when users visit your website
|
||||||
# using a Google Image Search results page).
|
# using a Google Image Search results page).
|
||||||
#
|
#
|
||||||
|
|
Loading…
Reference in New Issue