Site goes back to test page after certbot

Server
1

Hi. Ok, so I have a site through amazon aws. It’s been running for a few months now but with no https://

Today, I used letsencrypt certbot to get a certificate and now https:// is working but the site went back to the test page.

How do I get the site back? Thanks

2

Hi,

Can you please fill in the following form?

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. crt.sh | 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:

I ran this command:

It produced this output:

My web server is (include version):

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

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):

Thank you

3

Domain is betting-analyst.com

I ran these commands:

$ git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt
$ /opt/letsencrypt/letsencrypt-auto --debug

and also edited httpd.conf according to this https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-an-instance.html

<VirtualHost *:80>
DocumentRoot “/var/www/html”
ServerName “example.com”
ServerAlias “www.example.com”

web server is amazon linux ami 2018.03

Not sure of the OS… where do I find that?

Hosting provider is amazon and yes I can login to a root shell, I’m logged in right now through putty

4

Hi,

Can you try this command and try to locate your ssl (port 443) vHost?
apachectl -S

Thank you

5

I get this:

AH00526: Syntax error on line 7 of /etc/httpd/conf/httpd-le-ssl.conf:
SSLCertificateFile: file ‘/etc/letsencrypt/live/betting-analyst.com/fullchain.pem’ does not exist or is empty

First of all, thank you for taking the time to help me but just as an aside, I would be happy if I could just somehow remove the certificate and get it back to how it was before I try to add https again because I really need the site back up more than anything.

I’m really a novice at this but my thinking is that when the site was deployed through amazon, it was done some way that the site doesn’t reside at /var/www/html maybe?

6

Ok sorry to be all over the place but I went back to httpd.conf and edited out the DocumentRoot “/var/www/html” section. The http://betting-analyst is working again (sigh of relief lol) and the https:// still goes to the test page.

So I guess I just need the https:// to point to the developed site

7

Hi,

There are two issues…

First one, please try run ./certbot-auto certificates and share us the output…

Secondly, please go to /etc/httpd/conf/httpd-le-ssl.conf and see if there’s an existing document root (for that vHost), if not, please try to add the document root…

Thank you

8

Found the following certs:
Certificate Name: betting-analyst.com
Domains: betting-analyst.com www.betting-analyst.com
Expiry Date: 2018-10-29 18:42:41+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/betting-analyst.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/betting-analyst.com/privkey.pem

Going to the httpd-le-ssl.conf and editing out the document root did the trick. Not sure why editing it out works but I guess that’s something with amazon?

Anyway, a few other things… This is the place I got the initial instructions from…

I actually never got to the certificate generation section… didn’t even make the config.ini file directly before it… is this something I need to do even though it’s apparently working?

Also, when I type in just betting-analyst.com it defaults to http version… How do I default it to https?

The https version also loads very slowly for me compared to http. Any idea what could cause that?

9

Edit: The config.ini isn’t necessary as it’s specific to Amazon Linux 2 not AMI which is what I’m running. I’m still wondering if I need to do the certificate generation part though. Seems like a huge step but as of now, the http and https are both working (though https is a bit slow)