I am trying to set up SSL access to my server (who’d guessed it). My setup is the following:
domain christianzollner.com is permantently redirecting with masking to christianzollner.ddns.net (no-ip service) which is then pointing to my raspberry pi server.
I was able to set up the SSL certificate for christianzollner.ddns.net but I am struggling to set it up for the christianzollner.com domain and I ran out of clues. The command shown below is the latest one I tried, so I guess it’s a starting point. To me it seems somehow that the certbot isn’t following the forwarding from the top-level domain to the no-ip service - but really, I am just guessing.
I ran this command: sudo certbot certonly --apache -d christianzollner.com --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for christianzollner.com
Enabled Apache rewrite module
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. christianzollner.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://christianzollner.com/.well-known/acme-challenge/H_TK2a5UYnX01KWVO3Uj3cWw-bFaQNFXZP8cJq7Clzg: 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.
My web server is (include version):
Server version: Apache/2.4.38 (Raspbian)
Server built: 2019-10-15T19:53:42
The operating system my web server runs on is (include version): Raspbian Buster
My hosting provider, if applicable, is: self-hosted on my Raspi
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): cerbot 0.31.0
Thanks again, Herr Auer! I changed the CNAME record from my registrar to point to christianzollner.ddns.net and (after a little while) it worked! Great!
working with SSL. This is because my registrar won’t accept “@” in my CNAME record (is this normal?) and I can’t provide a (corret) static IP adress for an A record. I also tried forwarding christianzollner.com to https://christianzollner.ddns.net but then again, my registar automatically creates an A record with the IP adress of my top-level domain (where I can’t install certificates).