

1·
10 hours agoI think the music experience with Plex + Plexamp is still far better. That’s the main thing I use Plex for.
Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb
I think the music experience with Plex + Plexamp is still far better. That’s the main thing I use Plex for.
For DNS challenges, I personally prefer using acme-dns. It’s a separate DNS server that only serves ACME DNS challenges. I felt a bit uneasy using an access token for my actual DNS host since it grants full read/write access to every record. acme-dns reduces the attack surface.
Let’s Encrypt follows CNAMEs and supports IPv6-only DNS servers, so you could just run acme-dns on a spare IPv6 address (assuming your internet provider has a static IPv6 range, or you have a VPS with IPv6).
I haven’t tested it, but in the “select your DNS provider” step, see if acme-dns is in the dropdown list.