Skip to content

docs: update port forwarding to state it works without a wildcard with tunnel #4887

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.

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
merged 7 commits into from
Nov 9, 2022
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
#til it appears .md is required in the pre step
  • Loading branch information
ghuntley committed Nov 9, 2022
commit 6e6c210a6cb80e676f548d7a793e2fad4a1944e5
4 changes: 2 additions & 2 deletions docs/networking/port-forwarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,8 @@ For more examples, see `coder port-forward --help`.
## Dashboard

> To enable port forwarding via the dashboard, Coder must be configured with a
> [wildcard access URL](../admin/configure#wildcard-access-url). If an access
> URL is not specified, Coder will create [a publicly accessible URL](../admin/configure#tunnel)
> [wildcard access URL](../admin/configure.md#wildcard-access-url). If an access
> URL is not specified, Coder will create [a publicly accessible URL](../admin/configure.md#tunnel)
> to reverse proxy the deployment, and port forwarding will work. There is a
> known limitation where if the port forwarding URL length is greater than 63
> characters, port forwarding will not work.
Expand Down