VNC does not work with new version

[FlorianB]

Hello!

I'm trying to create a ticket with the API and open the VNC console using noVNC on a third party website. Although, I'm getting weird issues since I've upgraded the hostnode.

Before, everything was working fine and I were able to view the console from the website. But since I've upgraded to 4.3-8/15961f21, I'm facing a pretty weird issue. When I want to open the console, I'm getting the following error:

nc6: connection timed out
TASK ERROR: command '/bin/nc6 -l -p 5900 -w 10 -e '/usr/sbin/qm vncproxy 4332 2>/dev/null'' failed: exit code 1

This error is what I see in the proxmox webinterface after closing the console on the third party website. Before, I'm seeing no output in the command and the console keeps staying black ( without anything being loaded ).


Are there any thoughts on this? Anything that changed from the latest 4.x version to the one I upgraded to? Strangly, it says "nc6" while I'm not connecting using IPv6. I guess that could be the issue. Where should I look at to change that back to IPv4?


Best Regards,
Florian

 

[tom]

As the novnc works perfectly on the default web interface and you use a third party tools where its not working I have the feeling that the third party tools it the problem.

Please provide details, and also ask the vendor of this tool, we cannot give help or fix unknown third party tools.

 

[FlorianB]

This is not absolutely correct. I'm not using third-party tools. I've just taken the Proxmox API for PHP, create a ticket on the website and let the user connect over NoVNC, the same way you do it in your default web interface.

Also, exactly the same code I'm using right now and methods were working fine with 4.2 - do you know of any changes which could lead proxmox to take IPv6 instead of IPv4 ( this is my guess for the issue, as it uses nc6 - while I'm connecting over IPv4 ).

Which details should I provide?

 

[tom]

the php client is a third party tool, provided by a community member.

 

[FlorianB]

Even though it has no relation with the thing proxmox itself executes, as I'm not calling nc/nc6 anywhere.

 

[tom]

I understand your problem but you do custom queries and settings so we do not know what you do wrong. I suggest you analyse the code doing the novnc console from our web gui, maybe this helps to find the problem on your code.

 

[FlorianB]

There is no problem in my code as it was working properly before I upgraded. Before, I'm 100% sure that /bin/nc was used and _not_ /bin/nc6. Do you maybe know some file(s) which do calls to that executable? Was there anything changing from 4.2 to 4.3 regarding this?

I've been investigating my code for hours now and I didn't find any issues, that's why I posted here.

 

[dcsapak]

There is no problem in my code as it was working properly before I upgraded. Before, I'm 100% sure that /bin/nc was used and _not_ /bin/nc6. Do you maybe know some file(s) which do calls to that executable? Was there anything changing from 4.2 to 4.3 regarding this?

we use nc6 since 4.0, so no change here... maybe there is some other change involved? network? client?

 

[FlorianB]

we use nc6 since 4.0, so no change here... maybe there is some other change involved? network? client?

No, there was no change. Even though, I've found a solution to fix it. By using a letsencrypt signed SSL certificate for Proxmox ( thus, we have a valid SSL cert on the webif now ) it seems to work again on the third party side. Once we add a self-signed SSL cert, it stops working. Although we didn't have a valid SSL cert before either. Maybe there was some layer of security / SSL added in the new version?

Anyway, we found our solution and it works great. Thanks a lot for your assistance!

 

[dcsapak]

No, there was no change. Even though, I've found a solution to fix it. By using a letsencrypt signed SSL certificate for Proxmox ( thus, we have a valid SSL cert on the webif now ) it seems to work again on the third party side. Once we add a self-signed SSL cert, it stops working. Although we didn't have a valid SSL cert before either. Maybe there was some layer of security / SSL added in the new version?

what browser do you use? safari on macos has known issues with self signed certificates and secure websockets...

 

[FlorianB]

what browser do you use? safari on macos has known issues with self signed certificates and secure websockets...

I've tried it with Chrome, Mozilla Firefox and Internet Explorer, as well as with Edge. Didn't work for neither.