-
See 502 Bad Gateway
-
In the request, change https to http
-
See 502 Bad Gateway
-
bypass ELB by placing this in local /etc/hosts file
13.23.21.14 admin.ab.redacted.example.com
-
reload the request with http OR https
-
the request works
Those are redacted instructions that showed AWS support that something seemed amiss with the elastic load balancer.
M helped me activate tcpdump and we captured output while recreating the error in different capacities.
I have just uploaded the access.log file and tcpdump files and several log files from ELB. They are going to dig through them to try to figure out what is happening. So so glad to have the support!