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
Update docs/networking/port-forwarding.md
Thank you sir

Co-authored-by: Ammar Bandukwala <ammar@ammar.io>
  • Loading branch information
2 people authored and ghuntley committed Nov 9, 2022
commit 6818b287f9cd5f906b936f64e0e5fe6cc4eec715
2 changes: 1 addition & 1 deletion docs/networking/port-forwarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ For more examples, see `coder port-forward --help`.
> URL is not specified, Coder will create [a publicly accessible
> URL](../admin/configure#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 fordwarding will not work.
> URL length is greater than 63 characters, port forwarding will not work.

### From an arbitrary port

Expand Down