1 Answer
- Newest
- Most votes
- Most comments
0
Hello, the problem is solved. It is an incorrect name of the config file, which has been adopted in many forums. The file name must be: WebSocketsUpgrade.config.
answered 6 years ago
Relevant content
- asked a year ago
- asked 7 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- How do I mount an Amazon EFS volume to an application directory in an Elastic Beanstalk environment?AWS OFFICIALUpdated 23 days ago
- AWS OFFICIALUpdated 8 months ago