-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to run certbot --nginx - UnicodeDecodeError: 'ascii' #5236
Comments
We will look into this, as it is certainly something that we should handle, but to work around this, replace the double quotes in comment of |
|
For instance, the mime type files contains this lines:
g³ will make raise the UnicodeDecodeError
|
Thanks for the additional information! |
After reading a comment on another thread by user @egberts, I ran the following command:
That command found the offending character "´" in one .conf file in the comment. After removing it (you can edit comments as you wish) and reloading nginx, everything worked again. |
@TommyZG can u tell me change which file ? |
i found that when i use certbot-auto in windows remote, it throw me this error ,but when i use it in linux remote ,it works great |
I had the same problem. I've found the following workaround (on Ubuntu):
After doing it, running |
Hi! The reason is that if you have some non ascii letters in nginx config (even in comments!!!) it will not work. |
It was in one of my .conf files. You have others. It was in the comment line. |
I got a similar issue, it was in /etc/nginx/conf.d/default.conf line 13 to 17:
I removed those comments and it worked. |
Hy ✌🏻, |
Thanks, it worked for me. |
Running the Thanks a lot. |
Three years later and this is still a life saver. THANK YOU! |
This is a life saving, thanks |
After 5 years, still helping |
My operating system is (include version):
ArchLinux (Kernel 4.13.11-1)
I installed Certbot with (certbot-auto, OS package manager, pip, etc):
pacman -S cerbot-nginx
I ran this command and it produced this output:
cerbot --nginx
Certbot's behavior differed from what I expected because:
Here is a Certbot log showing the issue (if available):
Here is the relevant nginx server block or Apache virtualhost for the domain I am configuring:
The text was updated successfully, but these errors were encountered: