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.
The operating system my web server runs on is (include version): Linux
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): 0.30.2
But the Web-Service is reachable from the internet via port 80. (At least when I try to get the cert I do not see any FW problems. What can I check next?
? Yes, this is my domain. Why you think it is parked? I can access the host crbox.campo-randale.de via http. But the FW permit https, too. (just in the moment the FW drops the connections)
Visible Content: Multiple Choices The document name you requested ( /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de ) could not be found on this server. However, we found documents with names similar to the one you requested. Available documents: /./acme-challenge/check-your-website-dot-server-daten-dot-de (common basename) /…/acme-challenge/check-your-website-dot-server-daten-dot-de (common basename)
Visible Content: Multiple Choices The document name you requested ( /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de ) could not be found on this server. However, we found documents with names similar to the one you requested. Available documents: /./acme-challenge/check-your-website-dot-server-daten-dot-de (common basename) /…/acme-challenge/check-your-website-dot-server-daten-dot-de (common basename)
https has a typical error, so the tool checks http over port 443.
Visible Content: Access forbidden! You don't have permission to access the requested directory. There is either no index document or the directory is read-protected. If you think this is a server error, please contact the webmaster . Error 403 crbox.campo-randale.de Apache
Indeed there is a DocumentRoot for this vhost. But the comment line:
certbot -i apache -w /srv/www/htdocs/vhosts/crbox_campo-randale_de/nextcloud -d crbox.campo-randale.de give the same result...
certbot run -a webroot -i apache -w /srv/www/htdocs/vhosts/crbox_campo-randale_de/nextcloud/ -d crbox.campo-randale.de
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for crbox.campo-randale.de
Using the webroot path /srv/www/htdocs/vhosts/crbox_campo-randale_de/nextcloud for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. crbox.campo-randale.de (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://crbox.campo-randale.de/.well-known/acme-challenge/k57egdNMux2iLORNvVLbyE1Rmq46aGD-FuOnagvCDOU: Timeout during connect (likely firewall problem)
To 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.