Still the same error:
http://i.epvpimg.com/zWo4d.png
I rolled back with my old cert. When i start an VM, i get this:
Running as unit 100.scope.
kvm: -vnc unix:/var/run/qemu-server/100.vnc,x509,password: Failed to start VNC server: Our own certificate /etc/pve/local/pve-ssl.pem failed validation against /etc/pve/pve-root-ca.pem: The certificate hasn’t got a known issuer
TASK ERROR: start failed: command ‘/usr/bin/systemd-run —scope —slice qemu —unit 100 -p ‘KillMode=none’ -p ‘CPUShares=1000’ /usr/bin/kvm -id 100 -chardev ‘socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait’ -mon ‘chardev=qmp,mode=control’ -pidfile /var/run/qemu-server/100.pid -daemonize -smbios ‘type=1,uuid=158fd294-d4fc-4de7-ac30-465cd2e7e316’ -name vm100 -smp ‘1,sockets=1,cores=1,maxcpus=1’ -nodefaults -boot ‘menu=on,strict=on,reboot-timeout=1000’ -vga std -vnc unix:/var/run/qemu-server/100.vnc,x509,password -no-hpet -cpu ‘kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce’ -m 512 -k de -device ‘pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f’ -device ‘pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e’ -device ‘piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2’ -device ‘usb-tablet,id=tablet,bus=uhci.0,port=1’ -device ‘virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3’ -iscsi ‘initiator-name=iqn.1993-08.org.debian:01:3db8b5388a5’ -drive ‘file=/dev/zvol/rpool/data/vm-100-disk-1,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on’ -device ‘ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100’ -drive ‘file=/var/lib/vz/template/iso/debian-jessie-preseed.iso,if=none,id=drive-ide2,media=cdrom,aio=threads’ -device ‘ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200’ -netdev ‘type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown’ -device ‘e1000,mac=00:91:72:A9:8A:8E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300’ -rtc ‘driftfix=slew,base=localtime’ -global ‘kvm-pit.lost_tick_policy=discard» failed: exit code 1
Dear i keep getting the error message: Unable to connect to the graphic server error
i double checked my information, i’m using as hostname my local ip address as i would normally through the browser to access the proxmox gui
Any suggestion how to fix this?
Hi! From the message, I can deduce:
- proxmox-client successfully logs in to Proxmox and downloads the vv file
- remote-viewer is successfully started
Your problem is that the vv file does not appear to give you correct settings. It looks to me like the problem occurs after proxmox-client has completed, when virt-viewer attempts to connect to Proxmox itself.
Try to log in to your Proxmox web GUI and connect using Spice manually. The problem likeley occurs there as well.
Best
Kalsan
Hi Kalsan,
Foremost thank you for the quick reply.
The odd thing about this issue is i can connect to spice manually through the Proxmox web GUI without problems.
Spice/Proxmox downloads the vv file and opens in the viewer without any issues, so that’s why i went to your github issues page in the hope maybe you might have an idea or solution.
Kind regards,
Defendos.
Hi defentos,
Looks like you’re in for some good-ol’fashionned debugging. Intercept the .vv file downloaded by proxmox-client and compare it to the one you download manually. Virt-Viewer consumes the file, thus you must use a breakpoint or return statement before virt-viewer is started.
The point behind this is that the differences in the files might indicate why it doesn’t work.
Best,
Kalsan
Helo kalsan,
Intercepting the .vv file downloaded by the proxmox-client is easy enough gladly, but i dont understand what you mean by comparing it to the one downloaded manually, do you mean the file that your .jar program runs? if so how can i set up a breakpoint or return statement, i have zero knowledge about debugging sadly.
Would you mind guiding me in the right direction as i only have 1 .vv file at the moment which is from the proxmox-client
All other .vv files downloaded with your client are 0kb files in my temp folder.
Regards,
Defentos.
Hi Defentos
So basically when you’re in the Proxmox Web GUI and viewing a machine, there’s a button on the top right which allows you to connect to that machine. One option is viewing the machine via VNC, but there’s another that does so via SPICE. Use the latter and you’ll get a .vv file.
proxmox-client basically logs in, downloads that file and starts virt-viewer which then establishes the graphical connection. When virt-viewer opens the file, it consumes it and the file is deleted.
Best,
Kalsan
Hi defentos
Did this help? If so, the issue can be closed.
Best,
Kalsan
Hi!
The file is blank. I go to: «C:Users!user!AppDataLocalTempremote-viewer1439377951253735658.vv» and the file has 0kbs.
Is normal this? I think the problem is the file dosn’t have the required information to connect.
My command is:
java -jar proxmox-client.jar -h !ip! -p 8006 -u root -s !password! -r pam -c «C:Program FilesVirtViewer v11.0-256binremote-viewer.exe» -n proxmox1 -v 103
Ok! The problem was the IP. Change IP for «Fully qualified domain name», as you say in Usage, and it works!!! Thanks for your work @kalsan.
That was effective self-help! Glad it worked for you and thanks for documenting your solution.
Hi,
I am seeing this exact problem on windows 10 pro. It happened after a windows 10 update.
My virt-viewer version is: 11.0.256
I am able to download the .vv file and the .vv file has normal information. Nothing looks suspicious in it.
My firewall log does not show any traffic being blocked between windows 10 desktop and the PVE.
nmap scan from windows 10 to PVE also shows that port 3128 is open.
After days of Google search, this github issue resembles my issue closest and I could not find anything online that works on me.
Could you please give me some ideas on how to troubleshoot this issue?
This Github repo is about a script that downloads a vv file from Proxmox. Further, you are hijacking a closed issue to ask for help for an unrelated problem. Please use Stackexchange or a forum for your question. This issue tracker is meant for discussion regarding proxmox-client.
@kalsan sorry. I’ll find another place.
Go to Proxmox
nodes seem offline, can’t communicate, VM’s are running
(solved) I’ve got a bit of a serious issue here. in the middle of upgrading some VM’s and suddenly proxmox just…dies. I’m trying to backup some vm’s but the backup storage isn’t loading, the drop down window where you select where to backup to just spins. the VM’s are all up but i can’t see any of them. i’ve restarted the entire cluster but the nodes only stay connected for a few minutes. if i pvestatd restart, again everything is fine for a few minutes then it dies again. We’re on version 4.4-15/7599e35a (i know, i inherited this mess)
В моём случае, кажется всё было интересней…
При установке, установщик спросил на какой интерфейс (из двух) назначить мост, и после установки перепутал интерфейсы. Условно говоря, я говорю, привяжи мост к интерфейсу eno0, он привязал, а после перезагрузки, всё спуталось eno0 — стал интерфейс который не должен принимать участие в мосту. Поправил /etc/network/interfaces — и всё заработало. Вроде…
DALDON ★★★★★
(01.12.21 12:26:43 MSK)
- Ссылка
-
#1
Если вы обновили Proxmox 6 до Proxmox 7 и у вас сервер не загружается (не доступен по сети), то вероятно причина вызвана обновлением systemd в котором MAC адреса для виртуальных устройств генерируются автоматически (почти что рандомно) основываясь на имени девайса и machine id.
В общем решение простое, подключиться по IP-KVM (или аналогах), открыть файл interfaces
Код:
nano /etc/network/interfacesИ прописать в настройки vmbr0, MAC address, такой же как и у самого устройства enp8s0 (в моём случае такое имя устройства, у вас оно может отличаться.
Код:
auto lo
iface lo inet loopback
iface enp8s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 15.11.16.23/26
hwaddress fc:44:91:26:31:e6
gateway 15.11.16.13
bridge_ports enp8s0
bridge_stp off
bridge_fd 0Проверить какие MAC адреса заданы для сетевых устройств можно выполнив команду
Всё это описано в официальной документации по обновлению Proxmox 6 на 7-ую версию
Последнее редактирование: 15 Сен 2021