Selfhosted

42766 readers

1454 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:

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!

founded 2 years ago

MODERATORS

[email protected]

193

What's up, selfhosters? - Sunday thread (slrpnk.net)

submitted 1 week ago by [email protected] to c/[email protected]

228 comments fedilink hide all child comments

It's Sunday somewhere already so why wait?

Let us know what you set up lately, what kind of problems you currently think about or are running into, what new device you added to your homelab or what interesting service or article you found.

I'll post my ongoing things later/tomorrow but I didn't want to forget the post again.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 week ago (1 children)

Tried to setup custom domains using Nginx Proxy Manager and Let's Encrypt DNS-01 challenges so I wouldn't have to open any ports and it worked!... except not really?

Proxy Manager shows everything was successful but the domains don't go anywhere. It seems to be because the TP-Link router from my ISP does DNS Rebinding protection... with no option to turn it off apparently... why......

So now I don't know where to go. I'm not really fancying hosting DNS myself but if I can't fix this any other way then I guess I'll do it. Or maybe I should ditch the ISP TP-Link and get something I could flash OpenWRT on?

[–] [email protected] 3 points 1 week ago (1 children)

Is the ISP supplied box also your wifi?

If not, IMHO I'd use the ISP equipment as a pass-through modem (if possible on that model?) and have a separate OpenWRT / pfSense firewall do all the heavy lifting for DHCP, DNS, ad blocking, etc

Depends if you'd then need another WAP, of course

[–] [email protected] 1 points 1 week ago (1 children)

It is also my Wifi, yeah. I didn't even consider that'd complicate things further. It does have a "pass-through" option though.

[–] [email protected] 2 points 6 days ago

Presuming you can put OpenWRT on it, it'll be fine as a single box

IMHO, I just prefer having it all as separates and then fix / change / upgrade parts as I go - but I soon run out of places to hide them