Why is my origin status down?
You checked the status of your origin, and it's down.
Your origin status is down. It might be for one or more of the following reasons.
Initial health check might not be complete
Your origin might be down because the initial health check has not finished yet.
Wait for the health check interval to pass before checking again.
Security groups might not have been added yet
Your origin might be down because the security group rules have not been added yet.
Be sure the security group rules have been added.
Application error
Your origin might be down because the application responsible for responding to the health check queries might not be running properly or on the correct port.
Verify that the application is running on the correct port, and is operating properly.
Incorrect type selected for health check type
Your origin might be down because you specified HTTPS as your type of health check.
Make sure that a valid certificate exists on the origin. For a self-signed certificate, you can use the Don't validate certificate option for the health check.
Host header is not set
Your origin might be down because you specified an IP address for the origin and did not set the host header on the health check.
Set the host header. For more information, see Creating a health check.
Network interface limit
Your origin might be down because your subnet might have reached the limit for the number of network interfaces allowed.
Try again with a subnet that has available space, or remove interfaces from the current subnet to give space for the health check virtual server instance.