Skip to content

Comments

add reverse proxy support for SSH and VNC websocket + nginx config#43

Open
aderumier wants to merge 1 commit intoPegaProx:mainfrom
aderumier:main
Open

add reverse proxy support for SSH and VNC websocket + nginx config#43
aderumier wants to merge 1 commit intoPegaProx:mainfrom
aderumier:main

Conversation

@aderumier
Copy link
Contributor

Currently the vnc && ssh websockets ports send to the wss client are hardcoded to 5001 && 5002.

This patch assume that if client use port 80/443, it's using a production reverse proxy, and reuse this port the websocket connections

Currently the vnc && ssh websockets ports send to the wss client
are hardcoded to 5001 && 5002.

This patch assume that if client use port 80/443, it's using a production
reverse proxy, and reuse this port the websocket connections
@mkellermann97
Copy link
Contributor

Hi @aderumier,
We've looked into this. The issue is that most of our users don't use port 5000 – they're running on 443 + 2 or similar. Merging this could potentially break a lot of setups.
If you could include a fix for that in your implementation, we'd really appreciate it.

Regards,
Marcus

@mkellermann97 mkellermann97 self-assigned this Feb 14, 2026
@mkellermann97 mkellermann97 self-requested a review February 14, 2026 11:53
@mkellermann97 mkellermann97 added the question Further information is requested label Feb 14, 2026
@aderumier
Copy link
Contributor Author

hi, no problem, I'll look to add an option to enable reverse proxy, and find a way to return the correct port dynamically to the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

question Further information is requested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants