view the rest of the comments
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!
Last I checked, a wild card cert for *.yourdomain.com is NOT valid for test.local.yourdomain.com, but IS valid for test.yourdomain.com. Wildcard certs are not recursive as far as I know.
You're right but you can get a wildcard for that level as well.
Totally, you can easy do *.test.yourdomain.com and that's works just fine for certbot. Ive never used cloudflare so I'd assume the same setup should work.
Last I checked, which was honestly two or more years prior, CloudFlare doesn’t handle second level sub domains (I.E.
a.b.domain.ext
) properly… when I tried it, I could make the DNS records, it did resolve, but the certificates didn’t work. I don’t know if that has since changed.You likely wouldn't be using cloudflare for that level anyways, since you want it to work when you're offline you'd bypass them entirely with local DNS server, local reverse proxy+certs. You'd use something like certbot with let's encrypt which works fine. https://certbot.eff.org/