Certbot made website unavailable via domain

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: www.ordewittetafel.ga

I ran this command: sudo certbot --apache

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
No names were found in your configuration files. Please enter in your domain
name(s) (comma and/or space separated) (Enter ‘c’ to cancel): www.ordewittetafel.ga
Obtaining a new certificate
Created an SSL vhost at /etc/apache2/sites-available/000-default-le-ssl.conf
Enabled Apache socache_shmcb module
Enabled Apache ssl module
Deploying Certificate to VirtualHost /etc/apache2/sites-available/000-default-le-ssl.conf
Enabling available site: /etc/apache2/sites-available/000-default-le-ssl.conf

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.


1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you’re confident your site works on HTTPS. You can undo this
change by editing your web server’s configuration.


Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 2
Enabled Apache rewrite module
Redirecting vhost in /etc/apache2/sites-enabled/000-default.conf to ssl vhost in /etc/apache2/sites-available/000-default-le-ssl.conf


Congratulations! You have successfully enabled https://www.ordewittetafel.ga

You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=www.ordewittetafel.ga


IMPORTANT NOTES:

  • Congratulations! Your certificate and chain have been saved at:
    /etc/letsencrypt/live/www.ordewittetafel.ga/fullchain.pem
    Your key file has been saved at:
    /etc/letsencrypt/live/www.ordewittetafel.ga/privkey.pem
    Your cert will expire on 2019-10-06. 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”

  • If you like Certbot, please consider supporting our work by:

    Donating to ISRG / Let’s Encrypt: https://letsencrypt.org/donate
    Donating to EFF: https://eff.org/donate-le

My web server is (include version): Apache/2.4.29 (Ubuntu)

The operating system my web server runs on is (include version): ubuntu18.04.1

My hosting provider, if applicable, is:

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 0.31.0

So, I assume there is nothing wrong with the output. It’s just that after having certbot install the SSL certificate, I am unable to get to my website using the domain name. IP works fine and I’m 100% sure the domain name is configured correctly, it’s certbot that makes it so that I can’t get to my website using the domain name. I know port 443 should be port forwarded as well, and it is.

Note: To get to the website, don’t type “www.ordewittetafel.ga” as URL in your browser, rather type “www.ordewittetafel.ga/tab/homepage.php” to avoid all the tracers I put in there. To actually see the website working, here is the URL with IP-address to save you some DNS browsing “94.212.14.213/tab/homepage.php”

Do you have port 443 opened in your firewall and/or router (if applicable)?

I just thought of that upon posting this, and no, I didn’t, so I went here to close this and then I saw your comment and now I feel a bit stupid

Hi @KelvinBouma

checking your domain - that works - https://check-your-website.server-daten.de/?q=ordewittetafel.ga

There is a new certificate

CN=www.ordewittetafel.ga
	08.07.2019
	06.10.2019
expires in 90 days	www.ordewittetafel.ga - 1 entry

And a redirect http -> https:

Domainname Http-Status redirect Sec. G
http://www.ordewittetafel.ga/
94.212.14.213 301 https://www.ordewittetafel.ga/ 0.067 A
https://www.ordewittetafel.ga/
94.212.14.213 200 0.674 B
small content:
<!DOCTYPE html> <html lang="en"> <body> <script src="fingerprint.js"></script> <script> var fp = new Fingerprint({canvas: true}); var result = fp.get(); window.location.href = "tracer.php?fingerprint=" + result; </script> </body> </html>

And a script. So all looks good.

You have created 4 certificates:

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-07-08 2019-10-06 www.ordewittetafel.ga - 1 entries duplicate nr. 4
Let's Encrypt Authority X3 2019-07-08 2019-10-06 www.ordewittetafel.ga - 1 entries duplicate nr. 3
Let's Encrypt Authority X3 2019-07-04 2019-10-02 www.ordewittetafel.ga - 1 entries duplicate nr. 2
Let's Encrypt Authority X3 2019-07-04 2019-10-02 www.ordewittetafel.ga - 1 entries duplicate nr. 1

You need only one.

I just mentioned that I in fact solved it. I even marked the solution, so thank you, but it was already solved.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.