Selfhosted

46293 readers

641 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 2 years ago

MODERATORS

[email protected]

122

What steps do you take to secure your server and your selfhosted services? (lemmy.selfhostcat.com)

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

57 comments fedilink hide all child comments

Inspired by this comment to try to learn what I'm missing.

Cloudflare proxy
Reverse Proxy
Fail2ban
Docker containers on their own networks

Another concern I have is does it need to be on a separate machine on a vlan from the rest of the network or is that too much?

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

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

Containers can talk to each other without any ports exposed at all, they just need to be added to the same docker network.

[–] [email protected] 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

I was getting more at stacks on a host talking, ie: you have a postgres stack with PG and Pgadmin, but want to use it with other stacks or k8s swarm, without exposing the pg port outside the machine. You are controlling other containers from interacting except on the allowed ports, and keeping those port from being available off the host.

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

You can do that by joining the containers to the same docker network, you don't need to expose ports even to localhost.

[–] [email protected] 1 points 3 weeks ago

I mustn't be communicating well, but that's fine.