Forward non-http ports and non-localhost ips

[sibidharan]

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

[jsjoeio]

Can you elaborate "Spawn a service in a neighbour container"? Then I can try and reproduce this locally.

[aureliainnovatives]

I am facing relatively same problem. If I run a Node App on port 3000 via Code-Server container and NGinx Proxy module, it's not accessible via url/proxy/3000 port. How to get rid of proxy/ and allow it like URL:3000 ?

[jsjoeio]

Hmm 🤔 @code-asher any ideas on how this should work behind nginx?

[sibidharan]

Can you elaborate "Spawn a service in a neighbour container"? Then I can try and reproduce this locally.

Sorry for late response @jsjoeio

Hi,

For example, in a docker compose, I spawn 3 containers, one is MySQL, another one is Adminer and another one is my Apache+PHP+Codeserver containers. When these 3 containers are spawned, they are reachable within themselves. If I forward container-ip:3306 in my desktop vs code over SSH, it forwards container-ip:3306 over SSH to my localhost:3306.

If my codeserver can see any host:IP, it should be able to forward it. For now, it is just looking in localhost and not for the hosts/servers running on the same/reachable network, even if I specify host/ip. But this works correctly in my Desktop VS Code.

In the below example, a MongoDB service is running on that IP:port and my desktop VS code is able to port forward that.

If not MongoDB, at least the code-server should be able to forward HTTP, like adminer.

[jsjoeio]

Thanks for elaborating! I'm not sure how'd we implement this on the code-server side 🤔

@code-asher any ideas?

[code-asher]

I believe we have the proxy hardcoded to localhost right now so we will need to fix that.

[code-asher]

Uh I might have misread the question. For implementing maybe we can leave the IP alone if it is 172.*?

[code-asher]

Actually we should just always leave the IP alone I think and when it is missing then we default to localhost.