Selfhosted
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!
view the rest of the comments
protip: if you have RDP open, you WILL get hacked.
Is it that bad? I mean, I am not much concerned myself as I would not leave the port open to anything but a small IP range, but I thought that the protocol was fine once a random long password is used.
Don't think it's that bad, although there were a couple pretty nasty vulnerabilities in RDP a couple years(?) ago
I'm by no means a windows guy anymore. I mostly use linux. But yeah, I've been told many a time to not leave RDP open to the internet.
No, use a VPN to connect to the server, then connect to RDP inside the VPN.
I would always recommend this, no matter what! Same with SSH, just keep this closed to the outside world!
Restricting to a few source ips makes it pretty safe. The RDP protocol is pretty secure, but it is a common one for zero day vulnerabilities, and software makers often do dumb things that break it's security. So the general advice is to never expose RDP to the internet at large.