I installed Let’s Encrypt per the following tutorial:
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:
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.
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.
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
Click below to sign up and get $100 of credit to try our products over 60 days!
Hi all, I have been reading through a lottttttt of publications and I can’t find my answer yet. I’m running ubuntu 18.0 and nginx My server was running before installing certbot in http://IP:Port and now none of them are working http neither https.
Please!!! Help!!
I found a solution via LetsEncrypt forum.
If you’re having issue with Wordpress not displaying content and a page looks broken after you’ve run CertBot and installed SSL and now via https:// you got a broken page here’s a solution:
old value
124.22.11.22
change it to: www.mysite.com
I didn’t see what you guys changed to get solution.
In my caseL I got it all installed. but now it serves broken page. Any idea what’s wrong?
I´m having a similar problem to the op, but my DocumentRoot´s are correct in the generated configuration files. I did enable ssl with
a2enmod ssl
and it also told me it´s already enabled. Everything works fine with http, but with https nothing is reachable. The domain in the configs below I replaced withexample.at
. The first site is just a dummy index.html with one h1 tag, the other one well gitlab. As said both work fine without https. I don´t have ufw installed (might do that later once it works like this). The os is ubuntu 16.04.example.at.conf
Generated by certbot example.at-le-ssl.conf
gitlab.example.conf
Generated by certbot gitlab.example.at-le-ssl.conf
Output of
sudo apache2ctl -S
When running
netstat -plnt
it also sais apache is listening on port 443 and 80@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.Hi @redsteamsoftware
Did you check if HTTPS worked before redirecting? If not, then it could just be your firewall.
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.