Authentication is required for the SPICE connection

[Afox]

Hello,

I get this error when triggering SPICE Session via webinterface. Interesting is: It´s not for all VMs, only 2.

Machines are KVM, qxl driver is selected. I use virt-viewer on Linux.

Any idea to solve this? What password is needed here?

Regards,

Afox

 

[Afox]

nobody? this problem seems to be random. I don´t get it.

 

[tom]

check your system time.?

 

[Jorge A. Ponce]

Hello! .. I have the same problem, the system time is correct, both the host and guest.

 

[Afox]

hello, for me this error did not show up for a long time now. I also checked system time and saw nothing remarkable. I thought they fixed it in an update. If your system is not up to date, maybe updating can fix the issue.

Regards,

Afox

 

[Jorge A. Ponce]

hello, for me this error did not show up for a long time now. I also checked system time and saw nothing remarkable. I thought they fixed it in an update. If your system is not up to date, maybe updating can fix the issue.

Regards,

Afox

Good morning ... I'm using the latest version of Proxmox, 4.3 ... when Proxmox restart, returns to work, you open the file .vv smoothly, but the minute when I try to re-enter the same VM, asks authentication.

 

[Ionel]

Same problem here. Latest updates installed, system time correct and in sync on both client and server.
Anyone has a solution? As a workaround I am currently circumventing the problem by adding
args: -spice port=6301,addr=0.0.0.0,disable-ticketing
to the config file in /etc/pve/qemu-server/ddd.conf and connecting directly to the VM.

It would be nice to hear about a proper solution for this problem, though.

 

[fabian]

the ticket is only valid for 30 seconds, so if it asks for authentication, it is most likely a time problem. AFAIK there were no spice related changes in any of the recent updates..

 

[Ionel]

Thank you for your reply, Fabian.

I can guarantee though, that the time between requesting a ticket via GUI and the connect between the client and spiceproxy is definitely well below 5 secs (both client and server are in the same LAN).

This timeframe is even less when I use the script, which requests a ticket and then immediately launches remote-viewer.


Funny thing is, it affects only some VMs.

It seems it will remain a mystery for the time being.

p.s.
This problem affects two different pve-Installations on different Platforms at different premises.

Best regards

 

[Dorkhian]

I've the same problem and i change the SCSI Controller Type to the default LSI 53C895A and now no password needing for spice connexion to the VM. Maybe resolve your problem too.

 

[Ionel]

Thanks Dorkhian, but I doubt it is in any way related to the controller type chosen. It's a spiceproxy ticket problem and I guess your problem disappeared (for the time being) because you had to restart the VM.

But thanks anyway.

 

[ioaoue]

We have the same problem with Proxmox VE 4.3. I think the problem is in the SPICE port allocation algorithm. Under certain conditions PVE creates two virtual machines using the same port for SPICE, one listening on IPv4 address, and one on IPv6.

Example:

# netstat -lpn | grep 61003
tcp  0  0 127.0.0.1:61003  0.0.0.0:*  LISTEN  6316/kvm
tcp6  0  0 ::1:61003  :::*  LISTEN  3206/kvm

In this situation virt-viewer can connect to VM running with PID 6316 and can not connect to VM with PID 3206. If I stop the first VM virt-viewer will connect to the second VM.

I think this problem occures when several VMs are starting at the same time, for example at host startup.

 

[fabian]

We have the same problem with Proxmox VE 4.3. I think the problem is in the SPICE port allocation algorithm. Under certain conditions PVE creates two virtual machines using the same port for SPICE, one listening on IPv4 address, and one on IPv6.

Example:

# netstat -lpn | grep 61003
tcp  0  0 127.0.0.1:61003  0.0.0.0:*  LISTEN  6316/kvm
tcp6  0  0 ::1:61003  :::*  LISTEN  3206/kvm

In this situation virt-viewer can connect to VM running with PID 6316 and can not connect to VM with PID 3206. If I stop the first VM virt-viewer will connect to the second VM.

I think this problem occures when several VMs are starting at the same time, for example at host startup.

could you file a bug report at bugzilla.proxmox.com ? thanks!

 

[ioaoue]

could you file a bug report at bugzilla.proxmox.com ? thanks!

https://bugzilla.proxmox.com/show_bug.cgi?id=1229