Help us test renewal with "letsencrypt renew"

Client dev
5

Here some testing results and the hurdles I ran into. Running ./letsencrypt-auto renew resulted in some errors:

1st attempt:
...The error was Expected a numeric value for http01_port. ...
Editing the file /etc/letsencrypt/renewal/[my.domain].conf file solved this problem. I changed http01_port = None to http01_port = 80

2nd attempt:
The next error message was At least one of the (possibly) required ports is already taken..
I needed to stop the webserver: apache2ctl stop

3rd attempt
As one of the ‘early birds’ of Let’s encrypt’ I am currently stuck by the rate limit. My ISP is so kind to provide the possibility to register a subdomain and direct it to the fixed IP of the DSL. Because of the growing number of customers with a subdomain that use Let’s Encrypt I can’t renew: Error creating new cert :: Too many certificates already issued for: xs4all.nl. Skipping..
So my certificate has expired and I am not able to renew… :sob:

Before I tried the renew option I ran into some problems already posted by others, such as an inaccessible directory ./well-known:

  1. A restrictive .htaccess. Try (temporarily) removing/renaming .htaccess or better, create an alias.
  2. Insufficient rights for the web server to serve content. I ran from ./letsencrypt-auto as root while the webserver runs as user www-data and is not able to get the content in .well-known/acme-challenge. Alter permissions with chmod and chown.