0

We have a new Kubernetes stack on Azure, with ingresses set up and an Application Gateway for Containers, normal HTTP/HTTPS traffic seems to flow perfectly fine, but our websockets over WSS are all getting 403s.

  • The application works fine on AWS (in a ton of other environments, with load balancers, without, etc.)
  • When logging on our application as part of our websocket auth code, we never see the request come in (but we do see all the other requests being made), suggesting we never make it by the AGC
  • I see practically no configuration on the AGC though, nor do I see any ingress configuration that would suggest fixing WSS
  • Certs are fine, chain is good, etc.
Improve this question

1 Answer 1

Reset to default
1

According to Azure support, websockets are currently not yet supported by AGC. It seems to be on the roadmap, no ETA though.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.