this post was submitted on 22 Mar 2026
7 points (81.8% liked)

Selfhosted

58044 readers
981 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
7
[Solved] Hosting Dockerized website on VPS with Apache (lemmy.wtf)
submitted 1 week ago* (last edited 1 week ago) by bestbakerycookie@lemmy.wtf to c/selfhosted@lemmy.world
13 comments fedilink hide all child comments
 

I made a Docker container of a website that's difficult to deploy, and I can reliably deploy it on localhost on my personal machine. The container sets up an Apache server with all the files and config to run the website.

However, the story is different on my VPS running Ubuntu and Apache. I have two other websites running on the same VPS, each with different domains and running directly on the host without Docker. When I deploy the dockerized website, I can't access that site. I opened ports on UFW. The Docker container sets the site to run on port 8000, and I tried running a reverse proxy on just that site with Apache by defining a config pointing towards the internal Docker IP on port 8000, but no luck.

Now I'm thinking of running a reverse proxy, but I haven't found any guides covering my situation: routing websites on both the host machine and through Docker. nginx-proxy looks to cover only Docker containers, and the Apache reverse proxy couldn't access the Docker container.

What are my options here? I plan to dockerize everything eventually, but that will be sometime in the future and not right away.

you are viewing a single comment's thread
view the rest of the comments
[–] hendrik@palaver.p3x.de 3 points 1 week ago* (last edited 1 week ago)

Yeah, You'll have to do a lot more troubleshooting than this. Did Docker successfully bind to port 8000? Can you curl it from the VPS itself? Does the container and the things in it run properly? Are there any error messages in the logs?

I'm not a Docker expert, but I'd start with the docker commands which show if a container is running and which ports it actually binds. Maybe a ss -at. then do a curl http://localhost:8000/ and see if it returns your webpage. If it doesn't, you need to fix your webpage container first. Or see if you can come up with an easier method to deploy your website.

A reverse proxy in any shape or form, will require your website to run, first.