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.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I'm pretty sure there might be some arcane scripts for you that would help you. But you should clarify query a bit. What are the weird issues you're running into? Alternatively, if you're managing nginx and letsencrypt manually you could try:
I hear good things about Traefik. Basically all I need is a reverse proxy that will handle re-writing URLs and websockets and slapping some ssl and auth on it. If something is easier for that, I'm all ears.
All three options should cover those requirements. You should take a look at them and decide which suit you best.
I am using caddy and it is really nice. It automatically does lets encrypt, https redirection, reverse proxy headers and there is much less boilerplate and repetition in the config file.
Can't talk about anything but SD (using various UIs, mostly AUTOMATIC1111's and other variants of the official) but they "just work" behind traefik. Traefik does the SSL termination and figures out which service (ip + port) to talk to based on its config. By default it does ACME (Let's Encrypt) for you and handles passing websockets without the special config lines like you need in nginx (though that should be as easy as this). As long as the application is well written (which is not always the case in the ML world, haha) and uses relative URLs for links, most everything should "just work" behind a reverse proxy, or need a config flag or two telling them they can trust the proxied SSL/IP and stuff like that.
+1 for Traefik. I got tired of all of nginx's quirks. It's really powerful and I'm sure the combinations of achievable results are infinite with nginx... so for some use cases it makes sense. But seriously... almost every container I'm likely to deploy follows a fairly simple model and traefik to just "works" with everything I've tried so far. I have ALL the traefik config in docker compose labels so every single configuration element I need to spin up a container a second time or on a new host is in ONE place.
Not quite sure what your issues are but you do have to make sure websocket proxying is configured if the app uses it https://www.nginx.com/blog/websocket-nginx/
I also switched over to Caddy about a year ago. Got tired of messing around with scripts to make letsencrypt work. Caddy has a lot of good defaults so you don't have to worry about setting the right headers or any websocket configurations. Its really just as simple as specifying the hostname & the reverse_proxy directive
You should elaborate on the weird issues you're having. It would also help to know which specific services you want to host and maybe some cleaned up (= generalized, with no personal information or hostname) logs to pin down the various issues.
For most services there seems to be at least a basic apache or nginx config available. From there you can see what you probably have to adapt to your own config.