[Bug]: Unable to forward remotehost:port

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Safari
• Local OS: MacOS
• Remote OS: Linux
• Remote Architecture: amd64
• code-server --version: 4.8.0

Steps to Reproduce

1. Spawn a service in a neighbour container
2. Under ports, paste container-ip:host
3. It tells remotehost:port is forwarded, but it is unable to do

When I open the forwarded URL proxy, it says

connect ECONNREFUSED 0.0.0.0:8080

Expected

The service running at remotehost:port should be forwarded via web proxy

Actual

Only locally running ports are being forwarded and remorehost:port is not being forwarded unlike VS Code Desktop. It is not even respecting the host part and just attempting to forward a locally running port.

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?

• I cannot reproduce this in VS Code.
• I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

No response

[code-asher]

Great points and thank you for the links!!

I prefer the query parameter as well but I am concerned that the application itself might use query parameters and have one called ip or maybe it is an app with multiple pages and navigating to a page drops the ip query parameter.

If we embed it into the path on the other hand the application would not be able to mess it up.

We could make it a requirement that applications running behind code-server’s proxy specially treat the ip query variable if it exists but I could see that not going too well. XD

[benz0li]

@code-asher @jsjoeio Please make sure that proxying is restricted to the following ranges:

IPv4

• 10.0.0.0/8^1
• 172.16.0.0/12^1
• 192.168.0.0/16^1

plus 127.0.0.1^2/localhost.

IPv6

• fc00::/7^3

plus ::1^4/localhost.

Proxying to arbitrary IPs must be prevented.
👉 Otherwise, this opens up an incredible number of (undesirable) use cases.