Selfhosted

60093 readers

951 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

[Solved] Hosting Dockerized website on VPS with Apache (lemmy.wtf)

submitted 3 months ago* (last edited 3 months 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

[–] MangoPenguin@lemmy.blahaj.zone 7 points 3 months ago* (last edited 3 months ago) (1 children)

Start with basic diagnostics, see if apache is running inside the container, if it is can you curl from inside the container, if that works can you curl from the docker host, if that works did docker create the firewall rule to expose the port or is the VPS overriding things in some way?

If that all looks good, is there a VPS provider firewall in place outside the OS?

Gotta start with the basics.

[–] bestbakerycookie@lemmy.wtf 0 points 3 months ago* (last edited 3 months ago) (2 children)

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.

[–] liking625@lemmy.world 2 points 3 months ago* (last edited 3 months ago) (1 children)

Without knowing your config is hard... but let's try: Apache httpd needs "SSLProxyEngine on" directive to be able to proxy to https sites first (assuming you already loaded mod_proy and mod_proxy_httpd), and then when connecting it will check the name of the server as defined in the proxypass directive to see if the certificate on that server matches the name, it also looks for the date of expiration, if any of those fail it wont rev proxy, to ignore those you have to add directives for that, too, but better make sure names match and dates are fine.

[–] bestbakerycookie@lemmy.wtf 1 points 3 months ago

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

[–] MangoPenguin@lemmy.blahaj.zone 1 points 3 months ago

An SSL error is expected because you're using localhost and not the common name that the cert is issued for. But the fact that it's connecting and showing the error means the server is working.