Self Hosted - Self-hosting your services.

11699 readers

1 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed if topic has to do with selfhosting.
[email protected] is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

[email protected]

How private is a vps? (lemmy.ml)

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

32 comments fedilink hide all child comments

Can the vps provider not read everything on your server, unless it's explicitly encrypted?

I'm asking because I'm interested in self-hosting mainly as a way to get privacy respecting services where good hosted ones don't exist. I'm not sure I really want to deal with running my own hardware

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

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

Idk how to even attach it to a domain

[–] [email protected] 4 points 5 days ago

yeah theres a learning process before you can set it and forget if you dont have prior experience.

[–] [email protected] 3 points 5 days ago

The networking aspect will likely be the trickiest, but if you're already interested in administrating a VPS you can absolutely do it.

Have an ISP that doesn't block inbound connections. So far both Comcast and Verizon have been cool to me in that regard.
Configure your router to always give your host machine the same internal-network IP address.
Configure your router to forward any relevant ports (TCP/80 for insecure HTTP, e.g.) to the internal address you assigned to your host.
Go to ifconfig.me or similar to ascertain your public Internet IP address.
Buy a domain (Namecheap has been good to me for a decade) and change its A record to point to that address!

Not hard, but not exactly uncomplicated either.