[SOLVED] Spice error unable connect to graphic server?

I clicked and it opened immediately, the screen was connecting to graphic server and after 3 or 5 second ,unable to connect to.....like in picture
 
Moayad said:
Please check the journalctl -f during open it again.
Click to expand...
Jan 14 16:09:33 pve systemd[56138]: Listening on D-Bus User Message Bus Socket.
Jan 14 16:09:33 pve systemd[56138]: Reached target Sockets.
Jan 14 16:09:33 pve systemd[56138]: Reached target Basic System.
Jan 14 16:09:33 pve systemd[56138]: Reached target Default.
Jan 14 16:09:33 pve systemd[56138]: Startup finished in 55ms.
Jan 14 16:09:33 pve systemd[1]: Started User Manager for UID 0.
Jan 14 16:09:33 pve systemd[1]: Started Session 19 of user root.
Jan 14 16:09:33 pve spice-vdagentd[38568]: Error getting active session: No data available
Jan 14 16:09:33 pve spice-vdagentd[38568]: Error getting active session: No data available
Jan 14 16:09:33 pve login[56153]: ROOT LOGIN on '/dev/pts/0'
 
Moayad said:
is that occur on other VM or only on windows 7?
Click to expand...
I can not use spice for all vms and also can not install windows 7 64 bit, if i have subscription so you can help me to solve immediately?
 
Last edited:
Moayad said:
please post the output of pveversion -v
Click to expand...
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
Uncerm: 1.6-2
zfsutils-linux: 0.8.5-pve1
 
What is the virt-viewer version, also check if port 3128 is open on your node ss -a -4 | grep 3128 and firewall if enabled pve-firewall status?
 
Moayad said:
What is the virt-viewer version, also check if port 3128 is open on your node ss -a -4 | grep 3128 and firewall if enabled pve-firewall status?
Click to expand...
i use lastest ver virt-viewer 9.0 for client
root@pve:~# virt-viewer
Unable to init server: Could not connect: Connection refused

(virt-viewer:41996): Gtk-WARNING **: 21:14:41.013: cannot open display:
root@pve:~# ss -a -4 | grep 3128
tcp LISTEN 0 128 0.0.0.0:3128 0.0.0.0:*
root@pve:~# pve-firewall status
Status: disabled/running
 
Last edited:
Glad you solved your issue!

Please mark the thread as [SOLVED] to help other people who have the same issue Thanks!

Have a nice day :)
 
admjral3 said:
thank you for your support, i solved that avast block anything
Click to expand...
Hi, I am facing the exact same issue. Did you manage to setup an Avast exception or just disable it?

By trial and error I did determine that disabling Core Shields/Web Shield allow virt-viewer to successfully connect, but no matter what exception I try to configure (exe binaries, node web address, ip, etc.) I cant seem to get it working unless Web Shield is fully disabled.
 
vladconst said:
Hi, I am facing the exact same issue. Did you manage to setup an Avast exception or just disable it?

By trial and error I did determine that disabling Core Shields/Web Shield allow virt-viewer to successfully connect, but no matter what exception I try to configure (exe binaries, node web address, ip, etc.) I cant seem to get it working unless Web Shield is fully disabled.
Click to expand...
i just can disable avast,do you have any ideal for this?
 
In theory it should be enough to add to Avast exceptions https://<proxmox_server_address>:8006. But it doesn't seem to work, disabling the Web Shield entirely will allow virt-viewer to successfully connect.
However I have a few users who are anything but tech savvy that need to connect to an old WinXP machine and passthrough an USB device to it (so RDP is out of the question), I am quite reluctant to give such users the rights to disable their laptops antivirus :rolleyes:
 
Moayad said:
Glad you solved your issue!

Please mark the thread as [SOLVED] to help other people who have the same issue Thanks!

Have a nice day :)
Click to expand...
hi Moayad, i hope your are very good.

I was wondering if you can give me any help with my problem:

In the LAN i can open a spice connection from the webgui of proxmox to an VM (kali) but i try from outside the LAN (internet) and i can´t get the connection established.

I use PFsense for firewall and a open and forwarded port 3128 to the proxmox server.
 
You must log in or register to reply here.
Top Bottom