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
I would suggest signing up for a free Cloudflare account and setting up any DNS for your Pi through there, using the Cache feature.
Once that is done, setup an automated script that will pull down Cloudflare IPs into a file (you can use a cronjob to run this daily):
Then in your web server config to only accept connections from Cloudflare IPs:
I prefer this method over UFW/iptables block as it allows you to control the IP block per web config, so if needed, you can make exceptions by not adding the
include /etc/nginx/allow-cloudflare-only.conf;
into that specific site's conf file.And with Cloudflare you could also only open up port
443
, because Cloudflare will do HTTP ➡ HTTPS if you enable that in their settings.