1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
The shared error is related to wrong nginx configurations, which is out of scope of AWS premium support but I have shared the below links and information on best effort basis.
This issue seems to be related with the issue in nginx configurations, I could find some links where the same issue have been discussed you can check your configurations and what is missing.
Have a great day ahead !
answered a year ago
Relevant content
- asked 7 months ago
- asked 5 years ago
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 23 days ago
Hi Sanju,
Thanks for providing these links. However, I am not using nginx and only have the ALB pointing directly to the ECS cluster and was wondering if I could get this working without needing to setup nginx behind the ALB since hitting the public IP of the ECS instance already has the headers missing. Is there a way to preserve or add a header on ECS?
Thanks
Hi I am hitting similar problem and I am using Gorilla as webframework to deploy an app on ECS containers. I am getting 404 and I am kinda stuck and not able to move forward. I have not set up any NGINX config for this. Based on AWS documentation,it seems that working with websockets on ALB is no big deal. Was wondering if you were able to sort this problem
I am having the same issue as well with a mattermost server and have configured NGINX to add the headers