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: francium.informatik.uni-ulm.de
I ran this command:
certbot certonly --webroot -w /var/www/certbot --preferred-challenges http-01 --staging --email hans-georg.gloeckler@uni-ulm.de -d francium.informatik.uni-ulm.de --rsa-key-size 2048 --agree-tos --force-renewal
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for francium.informatik.uni-ulm.de
Using the webroot path /var/www/certbot for all unmatched domains.
Waiting for verification…
Challenge failed for domain francium.informatik.uni-ulm.de
http-01 challenge for francium.informatik.uni-ulm.de
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: francium.informatik.uni-ulm.de
Type: connection
Detail: Fetching
http://francium.informatik.uni-ulm.de/.well-known/acme-challenge/8d18gpIWGfPdvOn9KQ1iUW8RmJNsyk-sl3pe_Ee8rhI:
Too many redirectsTo fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
-
echo
-
echo ‘### Reloading nginx …’
Reloading nginx …
- docker-compose exec proxy nginx -s reload
2019/04/25 06:46:52 [emerg] 7#7: BIO_new_file("/etc/letsencrypt/live/francium.informatik.uni-ulm.de/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/etc/letsencrypt/live/francium.informatik.uni-ulm.de/fullchain.pem’,‘r’) error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/francium.informatik.uni-ulm.de/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/etc/letsencrypt/live/francium.informatik.uni-ulm.de/fullchain.pem’,‘r’) error:2006D080:BIO routines:BIO_new_file:no such file)
My web server is (include version):
nginx in docker container
The operating system my web server runs on is (include version):
docker image
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):