The actual problem depends on which error message you're getting.ampr.org doesn't seem to be opting out of certificate issuance with DNS CAA records, so you should be able to get one. However, the HTTP validation method will be the only one available to you. That means the machine you're running the ACME client on will need to be able to accept incoming connections on port 80 from the public Internet, at the IP address behind your FQDN.On Thu, Oct 30, 2025, 05:10 Mark Phillips via 44net <44net@mailman.ampr.org> wrote:Hi Folks,_______________________________________________I'm having some trouble trying to get LetsEncrypt SSL certificates authorised for use on my WWW devices. The issue seems to be that I do not have control of the TLD and so I can never authorise the issuing of the certificate.I've tried *.ni2o.ampr.org (generic catch all), fqdn.ni2o.ampr.org (device specific) and many other variations but they all fail at the authorizing of the cert.What am I doing wrong? I'm using LetEncrypt (free not-for-profit) SSL certificates successfully in other areas but i do control the domain for those.Thanks for your helpMark / G7LTT
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org