@ssergio, I’m pretty sure you’ve found a bug in Certbot which is ultimately based on one of the libraries that Certbot uses for communicating with the certificate authority. This library assumes that error messages from the CA will be in ASCII, but the protocol actually allows them to be UTF-8 Unicode. In this case the CA tried to verify a challenge on your server but received a 404 not found error in Russian, which for debugging purposes it then quoted back to Certbot. Certbot then crashed trying to interpret this error because it didn’t expect it to contain Unicode data.
I’ll have to file a bug about this (and thank you for letting us know!). It does appear that the problem is that your server is not serving the correct files at the correct location when attempting to verify the challenge.
You can check whether, for example, creating a file called
/projects/project-two.ru/public_html/test.txt results in that file being visible at http://project-two.ru/test.txt (which it should, if the
-w was specified correctly). A subsequent test is whether creating a file called
/projects/project-two.ru/public_html/.well-known/acme-challenge/test2.txt results in that file being visible at http://project-two.ru/.well-known/acme-challenge/test2.txt.