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. https://crt.sh/?q=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: affinityced.com
I ran this command: sudo certbot --apache
It produced this output:
sudo certbot --apache
Password:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Enter email address (used for urgent renewal and security notices) (Enter ‘c’ to
cancel): it@affinityced.com
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
(A)gree/©ancel: A
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let’s Encrypt project and the non-profit
organization that develops Certbot? We’d like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
(Y)es/(N)o: N
Which names would you like to activate HTTPS for?
1: privacy.sv.affinityced.com
[ … other sites deleted due to new user limitation ]
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 1
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for privacy.sv.affinityced.com
Waiting for verification…
Cleaning up challenges
Created an SSL vhost at /private/etc/apache2/extra/httpd-vhosts-le-ssl.conf
Deploying Certificate to VirtualHost /private/etc/apache2/extra/httpd-vhosts-le-ssl.conf
Enabling site /private/etc/apache2/extra/httpd-vhosts-le-ssl.conf by adding Include to root configuration
Error while running apachectl configtest.
AH00526: Syntax error on line 13 of /etc/letsencrypt/options-ssl-apache.conf:
Setting Compression mode unsupported; not implemented by the SSL library
Rolling back to previous server configuration…
Error while running apachectl configtest.
AH00526: Syntax error on line 13 of /etc/letsencrypt/options-ssl-apache.conf:
Setting Compression mode unsupported; not implemented by the SSL library
IMPORTANT NOTES:
- We were unable to install your certificate, however, we
successfully restored your server to its prior configuration.
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/privacy.sv.affinityced.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/privacy.sv.affinityced.com/privkey.pem
Your cert will expire on 2020-03-09. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the “certonly” option. To non-interactively renew all of
your certificates, run “certbot renew”
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
My web server is (include version):
Server version: Apache/2.4.41 (Unix)
Server built: Oct 17 2019 18:04:28
The operating system my web server runs on is (include version):
macOS 10.15.1 (Catalina)
My hosting provider, if applicable, is:
N/A — it’s our own machine
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 1.0.0
There is a similar thread on GitHub from May (https://github.com/certbot/certbot/issues/7063) where the answer basically was “we’re looking into it,” with no resolution. Since certbot backs out the configurations and deletes the .conf files, I’m at a bit of a loss for what to do next.
We’re hoping to use Let’s Encrypt for some one-off sites (since it seems that wildcards can only be used via Docker?) where a pesky consultant has convinced the owners that SSL is needed for sites with zero user interaction. We use paid certificates for other company properties and I would prefer not to have to pay $$$ for limited-use certificates if possible. Any suggestions for what to do to work around the SSL Compression problem are welcome.