> It is hard to set up. Really? > You have to configure every server to use the certificate A couple of lines in apache/nginx/other config? The same lines ea

> It is hard to set up. Really? > You have to configure every server to use the certificate A couple of lines in apache/nginx/other config? The same lines each time. You probably don't want your dev box to be doing things required for LE renewal (allowing external in for HTTP(S) validation, making public DNS changes for DNS01, …) but I have a small container doing that and other boxes pull the resulting cert from there (a small cron task, again the same in each instance). > and every client to accept the certificate > external devices, such as iPads. How do you [get] your certificate onto them? I suggested using a public name and an LE cert or similar. Clients will trust without extra effort. > We also use IPs instead of domains I did say “more devs don't” not “all devs don't”, there will of course be special cases. Though using addresses rather than names just feels broken. > And then your IP changes and all is lost again That is an argument against using address based config rather than name based config, not an argument against using HTTPS!