Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
Accepted Answer
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
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.
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.