Question

Installed LetsEncrypt and redirects to https work but web pages are no longer reachable

Posted on August 1, 2017
Let's Encrypt Apache
Asked by redsteamsoftware

I installed Let’s Encrypt per the following tutorial:

https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-16-04

Works to require a redirect to https but I can no longer reach the index.html web page or any other page on the site. I deleted the lines added by let’s encrypt to the .conf file for my site and now the site is reachable. I was trying to setup a password protection of the site per the following tutorial:

https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-apache-on-ubuntu-16-04

But instead of receiving a prompt for a username and password, I just received the following message in Google Chrome (and also could not reach pages in IE):

Not Found

The requested URL / was not found on this server.

Apache/2.4.18 (Ubuntu) Server at mysitename.com Port 443

the “mysitename.com” is just edited to not include my actual domain.

Any suggestions will be appreciated.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Flamber Hansen • August 5, 2017

Accepted Answer

@redsteamsoftware

The Let’s Encrypt install shouldn’t mess with the listeners, but if the configuration was a bit off to begin with, then the wizard sometimes does strange things.

Run this command to list which configuration files Apache is using:

sudo apache2ctl -S

And then post each configuration file it lists and /etc/apache2/apache.conf

Flamber Hansen • August 4, 2017

@redsteamsoftware

But the line you’ve posted says that Apache is only listening on 443 with IPv6. Use the </> button in the comment editor to insert console output, which doesn’t lose it’s formatting.

Flamber Hansen • August 1, 2017

Hi @redsteamsoftware

Did you check if HTTPS worked before redirecting? If not, then it could just be your firewall.

sudo ufw status

But without seeing your VirtualHost configurations (both), then it’s difficult to know the exact problem. Post them and hide your domain if you don’t want to share it.