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.
- 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:
> Any issues on the community? Report it using the report flag.
> Questions? DM the mods!
- 1 user online
- 218 users / day
- 9 users / week
- 244 users / month
- 841 users / 6 months
- 0 subscribers
- 542 Posts
- 8.93K Comments
- Modlog
I’m using DuckDNS, it has a plugin for pfSense / OpnSense.
I host my own ddns server in a debian container https://wiki.debian.org/DDNS
Here we go down another rabbit hole… 😆
I use DuckDNS. There’s been only one outage for the ~2 years I’ve been using it and it’s free. I also use DuckDNS to acquire the SSL certificates for the reverse proxy.
I also use duckdns, but in the last year it went down like twice or something. Its good but not really reliable.
I pay an extra £1 a month to my ISP to get a static address. Figured it’s well worth having no hassle.
If you only need public access to things like HTTP or SSH you don’t necessarily need to run dynamic ip and just setup Cloudflare Tunnels. So far I haven’t needed to put anything public that doesn’t run on the provided tunnels.
Where are the settings for these tunnels located in Cloudflare? I was looking around the website last night but didn’t have any luck.
Look under the Zero Trust category and then once there you’ll see another menu item called Access. There you’ll find Tunnels, in addition to Tunnels you can add an Application in the same Access menu to create policies that only allow certain clients to connect.