Console Proxy URL settings stop working after CPVM reboot

[itobin]

CS Version 4.22.0

We are using nginx reverse proxy to the CPVM.

When we set the console proxy to SSL and set a URL, restart the management server, the connections then work fine to the VMs using the new config and the NoVNC connections are secured over SSL... great.

Now the problem is that when we reboot the CPVM, this config no longer works. Instead the connections to the VM consoles timeout, there is no way to get it working again even after rebooting the CPVM several times.

We then have to remove the SSL and console proxy settings, reboot the management server and also reboot the CPVM to get it back to the defaults, then go through the process of settings SSL and URL again.

So it appears the console SSL and URL settings are only active until there is a CPVM reboot, then thats its and we have to start again.

Not sure where to look at trying to diagnose this problem.

[DaanHoogland]

@itobin when you say reboot, you mean from the MS web-console, or do you mean from inside the OS or from the host?

[itobin]

@itobin when you say reboot, you mean from the MS web-console, or do you mean from inside the OS or from the host?

it can be anything, so for example rebooting the CPVM from the Web Gui or rebooting the KVM host the CPVM resides on. The issue is easy to reproduce

[itobin]

a bit more info on this.

we logged into the console proxy before a reboot and ran netstat -nat

the ports are listening

We then rebooted the CPVM and ran netstat -nat again

so it looks like the ports stop listening which is causing the issue. Is this expected behaviour after enabling the URL and selecting SSL? If so what ports is it supposed to be listening on and why only after a reboot does this change?

[weizhouapache]

a bit more info on this.

we logged into the console proxy before a reboot and ran netstat -nat

the ports are listening

We then rebooted the CPVM and ran netstat -nat again

so it looks like the ports stop listening which is causing the issue. Is this expected behaviour after enabling the URL and selecting SSL? If so what ports is it supposed to be listening on and why only after a reboot does this change?

Can you stop and start the CPVM instead of reboot ?

[weizhouapache]

a bit more info on this.

we logged into the console proxy before a reboot and ran netstat -nat

the ports are listening

We then rebooted the CPVM and ran netstat -nat again

so it looks like the ports stop listening which is causing the issue. Is this expected behaviour after enabling the URL and selecting SSL? If so what ports is it supposed to be listening on and why only after a reboot does this change?

Can you stop and start the CPVM instead of reboot ?

[weizhouapache]

a bit more info on this.

we logged into the console proxy before a reboot and ran netstat -nat

the ports are listening

We then rebooted the CPVM and ran netstat -nat again

so it looks like the ports stop listening which is causing the issue. Is this expected behaviour after enabling the URL and selecting SSL? If so what ports is it supposed to be listening on and why only after a reboot does this change?

Can you stop and start the CPVM instead of reboot ?

[itobin]

@weizhouapache

exactly the same unfortunately

[weizhouapache]

@weizhouapache

exactly the same unfortunately

what's the status of cloud service in CPVM ?

[itobin]

looks ok I think