How do we change the default VNC Port (5900)?
It would be nice to have it on the Server / Cluster Edit Config Page.
It would be nice to have it on the Server / Cluster Edit Config Page.
Change default VNC Port
- Thread starter apmuthu
- Start date
The VNC port is dynamically allocated between 5900 and 6000. You can't change that.
- Dietmar
Port Redirection
Do we just redirect the ports 5900 to 6000 on the router to the host's LAN IP and expect it to show each VM correctly?
Do we just redirect the ports 5900 to 6000 on the router to the host's LAN IP and expect it to show each VM correctly?
C
CyberAng3l
Guest
Open the file "/usr/share/perl5/PVE/ConfigServer.pm" and find the line:
then change the number to the ports you like
I had to restart the whole proxmox machine for the changes to take effect.
Code:
"for (my $p = 5900; $p < 6000; $p++) {"then change the number to the ports you like
I had to restart the whole proxmox machine for the changes to take effect.
Please stop putting such hack into the wiki - Encouraging users to modify system files is a really bad thing. It is OK if you discuss that in the forum, but I wont get that documented in the wiki.
if you really think that option is needed, write a patch to make it configurable (and try to get it included into the official release).
C
CyberAng3l
Guest
Could you please put such an option in Proxmox 2 VE?
I needed that hack as I have setup a Proxmox VE 1.8 in my university and incoming connection to port 5900 are blocked for security reasons.
I do not have access to the university's firewall so that's the only real solution (or SSH tunnels) if you don't have full control of the network you setup Proxmox VE.
Last edited by a moderator:
I have removed the Category: HOWTO Wiki link (pending your decision) but the page remains in the Wiki for now - the caveat may be expanded to include a Warning page link that addresses Dietmar's concern or he can decide it's fate.
How does one submit patches to the PVE Codebase in the absence of version control being public? The patch submitted with or without mods in a Forum Post has not yet made it to the codebase and I have to hack it in each time the deb/tarball changes.
How does one submit patches to the PVE Codebase in the absence of version control being public? The patch submitted with or without mods in a Forum Post has not yet made it to the codebase and I have to hack it in each time the deb/tarball changes.
Hi, I have two servers at the office:
A.- (Production) pve version 1.9
B.- (Test) pve version 2.0 Beta 3
I´ve directed the router ports 5900-5950 to Server A . So I can remotely open VM consoles (for emergency use, as it is very slow)
I can not use console on Server B virtual machines, as seems that same ports are used, and they are re-directed by the router to Server A.
What is the 'correct' configuration for this purpose ?
It seems that using other ports on server B (as written on this post) could solve the problem, but would like an official solution, that will survive updates to official Version 2.0
Regards
A.- (Production) pve version 1.9
B.- (Test) pve version 2.0 Beta 3
I´ve directed the router ports 5900-5950 to Server A . So I can remotely open VM consoles (for emergency use, as it is very slow)
I can not use console on Server B virtual machines, as seems that same ports are used, and they are re-directed by the router to Server A.
What is the 'correct' configuration for this purpose ?
It seems that using other ports on server B (as written on this post) could solve the problem, but would like an official solution, that will survive updates to official Version 2.0
Regards
The only way without changing Proxmox defaults is to port forward the custom ports to the natted local default VNC ports - one router per proxmox or one wan IP per proxmox
Our software automatically tunnels the VNC connection if you use a standard installation (I dont really know what yor are doing).
I have TWO Servers after the same router (WAN connection).
On this router I have redirected ports 5900-5950 to Server A, that makes console's virtual machines VNC output are correctly redirected to server A.
As same port range is used on Server B, I can not make a difference on router settings to Server B. I would need that console VNC output of Server B could be redirected to ports 6000-6100 or similar. Then I could redirect this port range to Server B on WAN router.