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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
if you are open to learn something new: Caddy webserver has a dead simple config, fetches tls certs by default for you and works with crowdsec too
Caddy is fantastic, incredibly easy to configure and just works out of the box beautifully.
Do you have it on host or container. I'm thinking abour switching to caddy on my host and replacing nginx with it but just wan't to hear your experience with it.
I run it in its own separate VM. Normally I use containers for everything, but Caddy being the part that's most on the outside of my network, as it were, I wanted to separate off.
I'm open to using sothing like caddy or traefic, but my issue is I have a mix of packages hosted directly on system and in docker container's and as such need to proxy them all.
That's why I'm not using caddy or traefic.
Edit: rn my mix consists of about 16 diff containeraized stuff and another 4-5 not containerized stuff.
Edit2: Just now realized that they can be used on the host system's also. Would you recommend traefic or caddy?
If all was containerised, I'd recommend traefik for its impeccable container integration, but for a mix of bare metal and container services I'd go with Caddy.
I'm using Caddy (sometimes in a container or most of the time as system package) as reverse proxy mostly for containers
I try to minimize non-container services but they work well with Caddy too
Traefik is a tad more complex (still nowhere near Apache2 levels though) but scales more easily espcially if you only run containers and start/stop them programatically
Update: I have moved to caddy, planned a switch either way and this just pushed me to do it.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CA | (SSL) Certificate Authority |
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| SSL | Secure Sockets Layer, for transparent encryption |
| nginx | Popular HTTP server |
3 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #452 for this sub, first seen 24th Jan 2024, 12:25] [FAQ] [Full list] [Contact] [Source code]
You could not use the dns challenge?
Requires me to add cname record's, which beats the purpose of automation honestly. Will most likelly move to caddy.
I thought acme or certbot could handle the DNS entries with an API call to your DNS provider.
It may require another plugin though. Googling some variation of certbot acme automate DNS challenge will give you a dozen tutorials.
Certbot has no support for vultr dns, not even with plugins. Already check.
acme.sh seems to say it supports Vultr: https://github.com/acmesh-official/acme.sh/wiki/dnsapi2#dns_vultr
Is there a particular reason you are keeping your DNS there?
Nice ui, and I already have a vps there. My main dns provider is namecheap but made it use vultr under the hood because of the nice ui.
Being a bit pedantic, and could be wrong, but wouldn't that make Namecheap your registrar only, which registers whatever nameservers you give it for the domain you own with the relevant gTLD entity?
Yes
Fair enough, just throwing that out there as an option to move DNS somewhere that does have API access for certbot to use.
Switching to porkbun would make things a lot easier for you. DNS challenge is why I switched from Namecheap, and it's less expensive and considerably easier to administrate.
Namecheap API works just fine with Certbot DNS challenges for me, FWIW.
I used dehydrated for a while. It's a quite simple python script iirc. It's on github someplace.
If your domain registrar is porkbun and you use their DNS hosting, they can generate wildcard certificates for you. It is pretty convenient though a little bit scary, since they generate your key pair and retrieve the cert from letsencrypt. But, since they run your DNS, they could do almost the same thing without you even knowing.
You don't need it to parse your config. Just set it to manual mode with a cron job. You can manually copy the certs with a short script.
Hi already tried that, worked for one domain and then stopped working for every other domain.
Oh, I just assuming it would be one or 2 domains, my bad.
Yea, evem rn on the server I have about 13? or so domains, and still haven't migrated all my services over.
What CA are you getting your certificates from?
If Let's Encrypt, have you checked their alternative methods to certbot?
Yea I'm using let's encrypt. Juet wanted to hear opinions from people who are probably more experienced than me.
I'd say any project that's decently maintained and satisfies your use case is probably good enough. I found this that from the sound of it fits your use case: https://github.com/fffonion/lua-resty-acme
New Lemmy Post: Alternative to certbot for acquiring ssl certificates to use with nginx. (https://lemmy.world/post/11122593)
Tagging: #SelfHosted
(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md