Selfhosted
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 posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
Start with basic diagnostics, see if apache is running inside the container, if it is can you
curlfrom inside the container, if that works can youcurlfrom 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.
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:
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.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.
Thank you so much!
SSLProxyEnginewas the key. This tutorial covered my usecase and it was just what I needed. Much appreciated!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.