[SOLVED] vnc error in lxcs and node >_shell

[ieronymous]

Hello

I have the following issue in Proxmox ver 6.2-12, since I moved my server to a different location. The only difference was the internal network which I did change from segment 192.168.2.0 to 4.0. I am connecting via vpn. When connecting from a laptop on the remote side and trying vnc and shell from ther still getting the same error
I also changed the static ip of the lxc to the appropriate way but I cant lvnc into it nor to enter the shell from my node.
Keep getting error while trying to start console
failed waiting for client: failed to lookup address information: Temporary failure in name resolution
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/proxserv --perm Sys.Console -- /bin/login -f root' failed: exit code 1

Another thing notices is that when I m on my node under system/certificates there are 2 certificates there
pve-root-ca.pem
pve-ssl.pem
What I noticed is that at pve-ssl.pem at option subject Alternative name tab (last tab to the right) it points to the wrong previous ip 2.0 network and not the new one 4.0 but I have no way to edit that (since its self added) and change to the correct ip. Is there a way to remove it and make an ew one or edit the specific one? Just edited both Private and public key which are both stored in /etc/pve/nodes/[your node name]/
- private key : pve-ssl.key
- public key : pve-ssl.pem
but neither of them contained that ip info just the key.

Also pvecm updatecerts --force didnt make any change (rebooted also - so its not that I have a long time to reboot or something)

PS Vm's work ok and i can ssh into my node.

Any thoughts?????

Thank you

 

[Moayad]

Hi,

if you can access to your node through ssh and https, then you need to check the firewall and hosts file in /etc/hosts.

Another thing notices is that when I m on my node under system/certificates there are 2 certificates there
pve-root-ca.pem
pve-ssl.pem
What I noticed is that at pve-ssl.pem at option subject Alternative name tab (last tab to the right) it points to the wrong previous ip 2.0 network and not the new one 4.0 but I have no way to edit that (since its self added) and change to the correct ip. Is there a way to remove it and make an ew one or edit the specific one?

you can generate a new certificate with pvecm[1] by the following command: pvecm updatecerts --force


[1] https://pve.proxmox.com/pve-docs/pvecm.1.html

 

[ieronymous]

Hi,

if you can access to your node through ssh and https, then you need to check the firewall and hosts file in /etc/hosts.


you can generate a new certificate with pvecm[1] by the following command: pvecm updatecerts --force


[1] https://pve.proxmox.com/pve-docs/pvecm.1.html

Probably I ve edited my post while you had answered and you didnt notice that I already issued pvecm updatecerts --force comand and rebooted
Problem is now that during log in screen realm is empty and I cant write to that field or select the arrow to show up a drop down menu ans stuck in the log in screen

 

[Moayad]

try to open from another browser to see if the issue from cache

 

[ieronymous]

try to open from another browser to see if the issue from cache

did the trick but still having the same vnc 5900 port error waiting to respond
At least with nano /etc/hosts found that wrong ip corrected it and rebooted

New Edit After first editing the hosts file and changing the ip address to the correct one and after that issuing the command pvecm updatecerts --force, the ip is also correct now at the certification page but VNC error still there

Does the pvecm updatecerts --force creates these two files?
- private key : pve-ssl.key
- public key : pve-ssl.pem
is it safe to remove them first from cli and issue the command again or are these files generated only during installation of proxmox and I would cause more trouble .....

 

[ieronymous]

Fixed it ... Somehow I kept miss-looking at my node's -> system, -> DNS option that it had still the old ip address. Changed that and reloaded and everything is working now

Thank you @Moayad

 

[Moayad]

glad that you solve your issue yourself!

I guessed the problem from DNS, thanks for sharing your solution