Didn't mention but when I force the installation it's not working and I receive this error {'***@gmail.com': (554, b'5.7.1 ****@gmail.com: Relay access denied')}
[06.09.2023_13-22-20] Self signed SSL issued for ****.com.
We'll need to know more info than what you've provided. Had you posted in the Help category you would have been shown the form below. Please complete as much as you can.
It looks like you have multiple problems. If I had to guess it might be related to this
But, without more info there is little we could say about your problem
==========================
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Let acme.sh put their certs in their normal locations.
Then point the web service to use the acme.sh certs [from their locations].
Go back and remove certbot and all related directories [/etc/letsencrypt].
[back it up, before deleted it, if you have any doubts about any remaining uses]
It MUST have been installed at some point.
The path /etc/letsencrypt/ is created by it.
Perhaps it was already removed OR it was installed via some previous name [like: letsencrypt / letsencrypt-auto / certbot-auto]
Ok, so, it has been uninstalled.
That still leaves the /etc/letsencrypt/ directory behind.
And, unfortunately, someone decided to switch to acme.sh and tried to make that switch seamless and reused the same file path/names.
[which was not something that would be recommended in this forum]
Like I said before:
You are trying to get a cert from ZeroSSL not Let's Encrypt. One of the threads you linked to (this one) shows how to change to Let's Encrypt.
It's possible your gmail relay issue is related to ZeroSSL. I have never seen that when using Let's Encrypt. And, I don't usually help debug problems with acme.sh and ZeroSSL. Actually, I didn't notice it until now
