1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Check that the client can reach the ALB and that the ALB's security group is configured in your fargate backend.
관련 콘텐츠
AWS 공식업데이트됨 일 년 전
Check that the client can reach the ALB and that the ALB's security group is configured in your fargate backend.
The security group of the ALB and the service using the ALB is the same one of the fargate service without ALB. What is strange is that the connectivity depends on the client. If I test with wscat, I can connect to the fargate service with ALB. However, if I use other client (for example, minecraft), I cannot connect to it. Of course, I can connect with minecraft to the fargate service without ALB. What is wrong with the ALB?
Maybe there is something not standard with the minecraft websocket implementation?
But the only difference is ALB. Why ALB does not behave the same as the direct connection? The implementation of the websocket application must take care of the difference?
Anyone has any ideas?