Skip to content

Commit

Permalink
Do no use non-ASCII characters in loaded configs
Browse files Browse the repository at this point in the history
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`.
  • Loading branch information
Arkshine authored and LeoColomb committed Feb 5, 2020
1 parent 28cb47d commit d2f5972
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion h5bp/security/x-frame-options.conf
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
# https://tools.ietf.org/html/rfc7034#section-2.1.
#
# Keep in mind that while you could send the `X-Frame-Options` header for all
# of your websites 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
# using a Google Image Search results page).
#
Expand Down

0 comments on commit d2f5972

Please sign in to comment.