Skip to content

docs: correct the port-forwarding host-service floor to 1.26 #7013

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

Merged
saddlepaddle merged 1 commit into from
Aug 30, 2026
Merged

docs: correct the port-forwarding host-service floor to 1.26 #7013

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion apps/docs/content/docs/ports.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ When a workspace lives on a [remote host](/remote-access), the sidebar lists por

If a local process already uses the port, the row shows **local port busy**. Stop the local process from the row (when a Superset workspace started it), or pick **Use another port** to map the remote port to a free local port. The row then shows the mapping, for example `3000 → localhost:54321`.

Forwarding needs a host on the current relay running host-service 1.25 or newer. For other hosts, forward the port yourself.
Forwarding needs a host on the current relay running host-service 1.26 or newer. For other hosts, forward the port yourself.

### Forward a port yourself

Expand Down
2 changes: 1 addition & 1 deletion apps/docs/content/docs/remote-access.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ If a local process already uses the port, the row shows **local port busy** and

The remote server sees each forwarded connection as coming from its own loopback address — there is no real client IP. Only TCP is carried; anything UDP (WebRTC media, mDNS) does not ride the forward.

Forwarding needs a host on the current relay running host-service 1.25 or newer. For a host you reach some other way, [forward a port yourself](/ports#forward-a-port-yourself) with SSH or Tailscale.
Forwarding needs a host on the current relay running host-service 1.26 or newer. For a host you reach some other way, [forward a port yourself](/ports#forward-a-port-yourself) with SSH or Tailscale.

Forwarded traffic passes through the Superset relay, like terminal traffic does. A browser talking to a forwarded dev server sends whatever it normally would — cookies, auth headers, query strings — so treat a forwarded port like the remote service it reaches, not like localhost.

Expand Down
Loading