I installed let’s encrypt on my lightsail instance that was running Bitnami LAMP. I was having issues with my apache config that was causing the cors to not work. In attempting to fix that I crashed the instance and decided to delete and start again. So that message was from when I was trying to set up the replacement instance after deleting the first. Honestly the encryption has been complicating my debugging of this strange problem. But chrome (that I am sending the buffer from) requires encryption.
At this point I have decided to try Plesk, so I am trying to create a LAMP under Plesk. I tried to get the let’s encrypt going on the Plesk instance, but there was an issue with the URI and then, updating the nameservers. I got an email earlier today from go daddy telling me that the dns was updated. But I am out of town for the weekend. So I can’t try it.
So I will try to get plesk to install let’s encrypt again on Monday. I am using phpStorm/xdebug and chrome’s built in debugger to try to catch this cors problem.