Some really strange stuff has happened over night.
Working on a project hosted on EC2.
Deployed updates last night with success, with LetsEncrypt enabled.
Made more updates this morning, deployed and received the error:
Could not access the challenge file for the hosts/domains.
Battled with this for a while with no success.
Disabling LetsEncrypt and re-provisioning the server succeeds but the site now shows either 502 Gateway Error or 504 Gateway Timeout.
We decided it wouldn’t be a bad idea to spin up a new EC2 instance and provision it to see if that fixes the issue. After doing so, it still errors at LetsEncrypt. We disabled it and can provision just fine but still receive either 502 or 504 errors.
Spent a lot of time on this discourse today attempting all sorts of fixes with no success. Perhaps someone can chime in and pin point something I may be missing?