depends, a server is just a server. Its more about how you setup your domain and secure your site. My domains are all anon and I run my servers through cloudflare. You don't really see the actual server itself, just cloudflares gateway.
this post was submitted on 07 Jul 2023
26 points (93.3% liked)
Selfhosted
39435 readers
6 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:
- 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
This is the way. I'm routed through cloudflare with private registration as well. The exposed IPs belong to Cloudflare and only they and I know where it goes after that.
I have the same setup. You just need to make sure the domain info is private when you first register it because if the whois history is cached somewhere and your info was public before then it can still be found.
Thank you, now I'm getting to know cloudflare.At the moment there is some problem with a redirecting loop, but as I read itcould be a problem with my nginx config and https. Either way thank you
Make sure ssl is set to full or strict If using local certs as well. Want to skip local certs? Use cloudflared
It really depends, honestly. If your instance is hosted behind a tunnel that is served through some sort of IP farm somewhere without jurisdiction of your own country, and that it doesn't trace back to you in any way shape or form, then it's definitely better. But if you are just hosting on your personal IP address, and with a domain name that is yours and registered to your name, you are definitely 'exposed' in that way. Up to you how to deal with that though.
Your actual question has been answered but I want to add that it's also a boon to be public in terms of adding legitimacy and weight behind what you comment and post. I stake my real name and identity behind what I post. Basically the foundational idea behind Facebook before it turned into the beast it is today.
You can obfuscate your location with a reverse proxy. The biggest problem with self-hosting is what can get compromised if they get access inside your network as opposed to a VPS. Keeping up to date on what is publically facing for vulnerabilities starts to become a chore.
You can make it private only. And have it not block all of the federation except few. Server location is not necessarily your location. Just make sure you have log rotate and keep as few logs on the file system as possible: and use nicknames and nothing personal.
The only way that you would get caught is when the government is involved, unless somehow you have acquired the server or the domain using crypto.