Imo it’s quite nice to not have a public domain like cloud.example.com which is much longer and all the gold ones are taken anyway.

Putting these local ones in my dns server is no issue, but getting https to work seems like a pain. I set up caddy to use its own certificate authority, but even when installing the root certificate to windows, many programs still don’t truth it and most of them don’t show a useful error message. Additionally getting them to trust the certificate is fiddely and then try to explain that to your mom so she can use my cloud.

All this makes me thing about switching back to public subdomains so I can get lets encrypt certificates

  • ShimitarA
    link
    fedilink
    English
    arrow-up
    3
    ·
    20 minutes ago

    Using self signed as a route that it’s not going to work after you factor in service specific apps that refuse your self signed certs, phones where installing those certs is a pain, and the overall WAF where installing those certs might just put off family users.

    Add in the mix the new Android 17 fucking “feature” where apps need special permissions to access the local network … (Yeah, Dav5x, home assistant, even Firefox stopped working on my on Android until I figured this out after upgrading to 17). I will write a post on this topic later on today.