Selfhosted

60366 readers

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

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Setting up local Caddy with Porkbun (wiki.livingcartoon.org)

submitted 2 days ago by kiol@discuss.online to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

cross-posted from: https://discuss.online/post/41958206

Open to suggestions for managing Caddy for domains from Porkbun.

Porkbun itself is using Cloudflare.

Their Caddy module is confusing to setup due to API changes and older documentation.

I'd like to use a declarative json configuration, but first I just need Porkbun to play nice enough to work when adding subdomains via wildcard.

The Goal

Setup legit Let's Encrypt as wildcard locally to test services at *example.domain.com, then put them into production on mainsite wildcard *.domain.com on VPS or similar.

Seeking Advice

Can anyone advise on setup recommendations. I'm currently using Nginx, which I had no difficulty setting up with ACME challenge. Perhaps I'm approaching Caddy in the wrong way. Thanks for any ideas!

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

[–] Pika@sh.itjust.works 1 points 2 days ago* (last edited 2 days ago) (1 children)

I wasn't aware of that they managed registered domains the way they do. I may need to reconcider my certificate setup currently, as I currently run a certificate per service because its more secure and looked cleaner, but if they count x.website.com certificates as website.com certificates, its entirely possible that when they switch to short lived certificate defaults I may come close to that rate limit.

[–] i_am_not_a_robot@discuss.tchncs.de 2 points 2 days ago (1 children)

If they cut the validity time for certificates, I'd expect them to also increase the rate limits by a corresponding amount. It's not like they have anything to gain by making it so regular users can't use the service anymore. They can't upsell you to Lets Encrypt Premium with a higher rate limit.

[–] Pika@sh.itjust.works 1 points 2 days ago* (last edited 2 days ago)

Yea hopefully. I know that short lived certs is currently an additional parameter when requesting, hopefully when the default changes they will have a higher rate limit. That won't be for quite some time though I expect.