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 web server is (include version): apache2 version 2.4.29
The operating system my web server runs on is (include version): armhf ubuntu 18.04
My hosting provider, if applicable, is: localhost (reica.no-ip.org)
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): n/a
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.31.0-1
Installation of certificate all Ok
How do I set virtual host to respond to https ? https://reica.no-ip.org does not work. I tried “certbot enhance --redirect” but it failed.
Can anyone help?
BTW http works fine. Apache2 is working Ok.
Hi Juergen. You may have tried reica.no-ip.org while it was off line while I was trying to solve the [problem. The cert with id 981181481 was lost and I started again on another SD card and a new certificate using certbot.
There must be a configuration problem somewhere that prevents the system to listen on port 443. I am not new to linux but not very savvy of ssl stuff. My site (family stuff, photos and family trees) has been running for years as an http site. I am trying to make it more secure with ssl encryption. Maybe you can give me a few pointers in the right direction to solve the problem.
After certbot enhance --redirect (which now works!) I get the following after http://reica.no-ip.org :
Bad Request
Your browser sent a request that this server could not understand.
Reason: You’re speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.
Visible Content: Bad Request Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please. Apache/2.4.29 (Ubuntu) Server at reica.no-ip.org Port 443
https + port 80 has the standard Apache page:
Apache2 Ubuntu Default Page It works! This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems.
Do you have a wrong port forwarding? Looks like you use
port 80 extern -> port 443 intern, because the error message shows the port 443, but port 80 is connected.
Port forwarding always:
Port 80 extern -> port 80 intern
Port 443 extern -> port 443 intern
One more question: If I upgrade my OS, can I just lift out the ssl cert and key files and put them in the new system ? Or do I somehow have to renew the certificate ?