Hi @G3orgx,
It looks like you have some non-ASCII characters (maybe ñ or something) in a file in a way that confuses Certbot. This is definitely a bug in Certbot in this case because it should be willing to accept these characters without getting confused.
Several bugs related to this have been fixed in the past, but it appears that you've found another one that will still need to be fixed now. Since you're using certbot-auto, you probably already have the most recent version of Certbot, so I can't simply suggest fixing this by upgrading to a newer version. 
Can you help find what the non-ASCII character in question is by looking at the files that were mentioned here?
One thing to help search for these quickly is grep -P '[^\x00-\x7f]', for example
grep -r -P '[^\x00-\x7f]' /etc/apache2 /etc/letsencrypt
If you find this character, maybe you can post the associated file so that we can better understand the nature of this bug and try to fix it.
Once you've found it, you can probably get your certificate right away by deleting the non-ASCII character (although of course you shouldn't have to do that in general, it may be necessary right now as a temporary workaround). If you need a certificate quickly, you could also try one of the other clients
which might not have the same bug. Most of the other clients are not quite as integrated with Apache, so for example they will not edit your Apache configuration for you to install the certificate after it's been issued, the way Certbot does.