Skip to content

fix(edge): add websocket support for lb origins #5912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RoRoJ wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(edge): add websocket support for lb origins #5912

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0da5dd1
fix(edge): add websocket support for lbs
RoRoJ Dec 3, 2025
7f0e21e
fix(edge): typo
RoRoJ Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions pages/edge-services/how-to/create-pipeline-lb.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,16 @@ If you see the message `Edge Services was unable to contact the host via the Loa
- **Origin host**: Ensure that you entered the correct origin host, with no typos, for a host that exists behind the selected Load Balancer.
- **Load Balancer ACLs**: Ensure that there are no [ACLs](/load-balancer/how-to/create-manage-acls/) configured on your Load Balancer which are blocking traffic from Edge Services.

## WebSocket support

If you want Edge Services to be able to forward WebSocket requests to the Load Balancer, you must enable a specific parameter via the Edge Services API.

Make a call to the [Update backend stage](https://www.scaleway.com/en/developers/api/edge-services/#path-backend-stages-update-backend-stage) endpoint, to enable the `has_websocket` parameter in the `scalway_lb` object.

If you do not enable `has_websocket`, WebSocket requests will not be forwarded to the Load Balancer. This means that any client attempting to establish a WebSocket connection to the Load Balancer origin via Edge Services will experience a failed connection or a 400/500 HTTP error.

This parameter cannot yet be set via the Scaleway console.

## Help for Kubernetes Load Balancers

If you are setting up an Edge Services pipeline for a [Kubernetes Kapsule](/kubernetes) Load Balancer, follow these steps to determine which Load Balancer and frontend to configure for your pipeline:
Expand Down