Maybe it’s unable to parse one of the Apache configuration files?
That could be the case.
Try this
cd /opt/certbot/
sudo ./certbot-auto certonly --standalone --agree-tos --rsa-key-size 4096 -d sb.pyroman.io --renew-by-default --dry-runqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Obtaining a new certificate x
x Performing the following challenges: x
x tls-sni-01 challenge for sub.mydomain.com x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Could not bind TCP port 443 because it x
x is already in use by another process on x
x this system (such as a web server). x
x Please stop the program in question and x
x then try again. x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x < OK > x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
An unexpected error occurred:
TypeError: object of type 'NoneType' has no len()
Please see the logfiles in /var/log/letsencrypt for more details.
Stop your web server Nginx/Apache first and then run that command again.
It worked:
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Saving debug log to /var/log/letsencrypt/letsencrypt.log x
x Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org x
x Obtaining a new certificate x
x Performing the following challenges: x
x tls-sni-01 challenge for sub.mydomain.com x
x Waiting for verification... x
x Cleaning up challenges x
x Generating key (4096 bits): x
x /etc/letsencrypt/keys/0000_key-certbot.pem x
x Creating CSR: /etc/letsencrypt/csr/0000_csr-certbot.pem x
x x
x x
x x
x x
x x
x x
x x
x x
x x
x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
IMPORTANT NOTES:
- The dry run was successful.
Okay so then it is definitely failing on one of your apache config files. You can however still generate certs like this using standalone but you will always have to stop your web server. That’s a temp solution but you should find out what you changed in Apache since this problem started.
So if you cannot find the Apache fault now then simply stop the web server and generate your cert and then restart your web server and manually install the new certificates in the Vhost
sudo ./certbot-auto certonly --standalone --agree-tos --rsa-key-size 4096 -d sb.pyroman.io -m youremail@address.com --renew-by-default
1 Like
Alright, thank you for help.
1 Like
No problem, glad I and some others suggestions helped narrow this down for you. Now you at least know where to start looking for the problem and you have a temporary workaround. Enjoy
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.