aws-amplify / aws-amplify/amplify-hosting
502 ERROR on opening website
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
### How did you install the Amplify CLI?
_No response_
### If applicable, what version of Node.js are you using?
_No response_
### Amplify CLI Version
5.1.2
### What operating system are you using?
Ubuntu
### Amplify Categories
storage
### Amplify Commands
Not applicable
### Describe the bug
On opening the website, I am getting
> The request could not be satisfied.
>
> The Lambda function returned an invalid origin configuration: One or more HeaderName or HeaderValue values are invalid. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

App Id: d2xsoqz50q03z2
Region: ap-south-1
### Expected behavior
The UI should open as it used to 1 week back. We didn't change anything since.
### Reproduction steps
1. Open the website.
### GraphQL schema(s)
_No response_
### Log output
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start by reviewing the Amplify Hosting configuration for app d2xsoqz50q03z2 in ap-south-1 and the CloudFront error about invalid Lambda origin headers. Compare the current deployment with the last known working state and verify that the website opens successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100