53
Be a VPS for other people?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2023
53 points (92.1% liked)
Selfhosted
38652 readers
357 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
It can be done. It's not worth the work involved. You could firewall off the two proxmox instances from each other and your own network. Then allow VPN access into the environment. You'll have to allow the machines access to the Internet to get software updates. The moment you do that you're opening the door to them making an outbound tunnel to make services publicly accessible. Then you've got every bot on the internet scanning your services for vulnerabilities/exploits.
Access to the outside world is where I start to not know what to do. If this was just locally run, I know how it would try and attack it, but the fact they they have to have access to the internet, that’s a hurdle I do not know how to get over.