Thank you so much! SSLProxyEngine was the key. This tutorial covered my usecase and it was just what I needed. Much appreciated!

Thanks for the reply. I can see that the port is bound and I enabled the ports in UFW. I have a hybrid setup where the other two websites are run directly on the host without Docker and now I’m introducing a Docker container for the new deployment. All sites are running on the same ports with different domains, but the Docker one is the one with an issue. How can I have the reverse proxy acknowledge both the site on the Docker container and the sites run natively? Should I set different ports in the Apache site configs then use those ports in the reverse proxy?

I realized I didn’t specify that the other two websites on the VPS are running directly on the host, without docker. I updated the post with that note.

Thanks for your reply. Yes, I can access with curl inside the container. The problem seems to be with SSL and I can’t figure out why:

curl https://127.0.0.1:8000/
curl: (60) SSL: no alternative certificate subject name matches target host name '127.0.0.1'

I’m using the same certs that the host machine uses. When I bypass authentication with curl -k https://127.0.0.1:8000/ it outputs the contents of the page. I don’t believe there’s a VPS firewall since I have another service running on a higher-numbered port which is accessible from the outside.