Selfhosted

40246 readers

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

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 1 year ago

MODERATORS

[email protected]

Need help: accessing all my containers by name (yall.theatl.social)

submitted 1 year ago by [email protected] to c/[email protected]

34 comments fedilink hide all child comments

I’m to the point now where my little home device has enough services and such that bookmarking them all as http://nas-address:port is annoying me. I’ve got 3 docker stacks going on (I think) and 2 networks on my Synology. What’s the best or easiest way to be able to reach them by e.g. http://pi-hole and such?

I’m running all on a Synology 920+ behind a modem/router from my ISP so everything is on 192.168.1.0/24 subnet, and I’ve got Tailscale on it with it as an exit node if that helps.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago (2 children)

Ugh. I really gotta switch to this. I started out by using Apache because that's what I use for work, and just what I know. I create the configs and get the certificates from Let's Encrypt manually. But now I have so many services that switching to something else feels daunting. But it's kind of a pain in the ass every time I add something new.

[–] [email protected] 2 points 1 year ago (1 children)

Other than writing an entry in my docker-compose.yml that was all the configuration required. The rest is in the GUI and it's super simple.

[–] [email protected] 1 points 1 year ago (1 children)

Oh, I don't have a GUI for my server. But I'm sure they have a command line interface for it, right?

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

I mean nginx proxy manager is managed by a GUI/web interface.

[–] [email protected] 2 points 1 year ago

Oh right a web interface. That makes more sense. 😅

Yeah, I really do need to get around to setting that up............

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

get the certificates from Let’s Encrypt manually

https://httpd.apache.org/docs/2.4/mod/mod_md.html just add MDomain myapp.example.org to your config and it will generate Let' Encrypt certs automatically

it’s kind of a pain in the ass every time I add something new.

You will have to do some reverse proxy configuration every time you add a new app, regardless of the method (RP management GUIs are just fancy GUIs on top of the config file, "auto-discovery" solutions link traefik/caddy require you to add your RP config as docker labels). The way I deal with it, is having a basic RP config template for new applications [1]. Most of the time ProxyPass/ProxyPassReverse is enough, unless the app documentation says otherwise.