If you could submit the log files via the “Report problem” link on the bottom?
Since you are on AWS, you could put CloudFront in front of it? The Let’s encrypt certificate should definitely be sufficient, but your instance needs to be reachable form the Let’s encrypt servers on port 80 + 443…
At the moment, we do not allow 80 and 443 out so that would be the cause of this error I believe. The third party cert we would like to bind already has it’s chain trusted by our devices. We also would like the domain it is in to match our corporate .com vanity URL. Is there a way to manually bind a cert to the web instance while keeping that change across updates when using the AMI? I agree that couldfront is an option but one we are not set up to take advantage of at the moment.
Ok, will look into adding that. I guess you have a .pem file and a .key file and they’d both need to be uploaded to the appliance + the domain configured…