You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to direct traffic from the Browser to the Signal component of Ion Pion (webRTC).
From our limited understanding, a websocket is established between the Browser and the Signal, and subsequent interactions take place via gRPC over this websocket.
The setup is verified ok with Traefik ingress. ie. a Browser is able to reach the Signal service with HTTP code 101.
When accessing signal.external, HTTP error 503 is observed. The endpoint Signal service does not seem to be receiving the traffic as there's no logging registered at the service, nor at its Istio Proxy.
What is the recommended setup for gRPC over websocket connections?
How else can we debug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We would like to direct traffic from the Browser to the Signal component of Ion Pion (webRTC).
From our limited understanding, a websocket is established between the Browser and the Signal, and subsequent interactions take place via gRPC over this websocket.
The setup is verified ok with Traefik ingress. ie. a Browser is able to reach the Signal service with HTTP code 101.
For this Istio setup, the Gateway is set for:
and the Virtual Service:
When accessing
signal.external
, HTTP error 503 is observed. The endpoint Signal service does not seem to be receiving the traffic as there's no logging registered at the service, nor at its Istio Proxy.What is the recommended setup for gRPC over websocket connections?
How else can we debug?
Beta Was this translation helpful? Give feedback.
All reactions