- Newest
- Most votes
- Most comments
Hello,
Not Found error usually occurs when the Requested Object/File is not present in the Server or the Requested location, so can you please check the Server or the requested location if the particular requested file is present
The error message is clearly coming from Apache indicating the requested object is not found. The apache logs would be a good place to start for troubleshooting. However, if this behaviour is new since configuring CloudFront, it might be due to the host header value: CloudFront will set the Host header to the origin DNS domain name when making requests to it, unless you configure it to forward the Host header: https://aws.amazon.com/premiumsupport/knowledge-center/configure-cloudfront-to-forward-headers/
Could it be that you've configured apache to respond to requests for www.example.com and not ec2-xxxxx.amazonaws.com?
Relevant content
- asked a year ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks for the reply.
Deployed app and all the files were reachable prior to cloudfront configuration. Obviously there is no change in the files or there location now.
https://xxxxx.com/api/auth/login << is the URL that fails, not sure the routing via "https://xxxxx.com" is appropriate or should it be "/api/auth/"