Proxmox novnc ошибка подключения к серверу - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

Greetings!

My first Proxmox VE and it’s working incredibly well! All of my VMs work fine, no problems other than the problem defined below.

However, I do have a minor problem when attempting to use the WebGUI Interface and the Console section under each VM. The error is stated as «noVNC — failed to connect to server». This appears at the top of the console section that remains black, and it only impact me while I’m using Chrome or Edge Chromium. It seems to work fine when using Firefox.

My install is fresh on Proxmox CE 7.1-10, and Chrome is my browser of choice.

I have tried the following:

disabled Chrome security for a few minutes (Settings > Security & Privacy > Security > No Protection) and that did not help whatsoever.
I have tried using a different Display such as VMWare, Standard VGA, and VirtIO-GPU, and rebooted each VM after each change to no avail.
I have tried to switch to a different TTY with Ctrl + Alt + F1 or Ctrl + Alt + F2, but this did nothing as well.

This happens for both my Linux VMs (Ubuntu) and my single Windows VM.

Last edited: Jan 31, 2022

oguz

Proxmox Retired Staff

hi,

This appears at the top of the console section that remains black, and it only impact me while I’m using Chrome or Edge Chromium. It seems to work fine when using Firefox.

seems to be a browser issue in that case (if it works with one but not the others, then likely it’s not an issue on the PVE end).

maybe you have some add-ons on your chrome/edge that are messing with it? have you tried clearing browser cache and/or using incognito mode without extensions?

it’s also possible that some antivirus software don’t like your browser making external connections (various internet security etc. software can block this)

oguz

Proxmox Retired Staff

I would entirely agree that it is something to do with the way that Chrome (and by extension Edge Chromium) operates

could you tell us which versions of the browsers you’re using?

also are you on windows 10 or 11? or which version?

and rebooted each VM after each change to no avail.

the VM settings should be fine (since it works in firefox). please revert them if you haven’t (to avoid false positives while testing for this issue)

Is there a better way to get the HTTPS certificate issue fixed?

how do you mean?
did you add a custom certificate? how exactly did you do so?
which HTTPS error are you talking about? could you send a screenshot please?

Источник

22 Jan 2017 | Автор: dd |

Неспешно знакомлюсь с системой виртуализации ProxMox VE, которая примечательна тем, что из коробки поддерживает одновременно KVM и OpenVZ. И, помимо этого, при крайне простом веб-интерфейсе, поддерживает все фичи виртуализации KVM в бесплатном режиме, хотя и выкидывает, при каждом заходе в админку, уведомление “у вас отсутствует подписка”. Что разительно отличает данную систему от VMware ESXi, которая в бесплатном режиме держит всего один камень, а также требует, как минимум, 2IP для создания виртуальной фермы серверов, ибо один забирает под сервер и не имеет собственной реализации NAT.

Всем удобная система, но напоролся на отвратительный баг, по которому в Mozilla Firefox с завидным постоянством отваливается браузерная noVNC консоль доступа к виртуальной машине через веб-консоль управления. Соединение просто прекращается, показывает форму логина и выдает ошибку Server disconnected (code: 1006). Причем наглухо, так что приходится скакать с бубном, пытаясь реанимировать noVNC соединение, ибо все новые начинают запускаться с этой же ошибкой.

Что только не ковырял, но лечится это только путем удаления куков для урла вебморды ProxMox и перечиткой сертификата, находящегося в разделе Дополнительно -> Сертификаты -> Просмотр сертификатов -> Серверы -> PVE Cluster Manager CA

Но поскольку noVNC консоль висла каждые пару минут, то стал искать пути как с этим жить и что делать, ибо в Vivaldi оказались те же проблемы. И случайно обнаружил очень занятный ценебаг-цефич: у меня установлена Mozilla Aurora, еще со времен протечки памяти Firefox. И вот при запуске Aurora стартует тот же самый Firefox 50.1.0, просто вторым окном. Но из него noVNC соединение работает вообще без нареканий, а из первого окна, где постоянно отваливалось – теперь максимум что, может зависнуть сессия noVNC, которую просто закрываешь и стартуешь новую консоль.

Очень странно конечно, но не менее странно, чем отвал сертификата ProxMox в процессе работы.

Еще одним вариантом быстрого доступа к консоли виртуальной машины с проблемами noVNC, является использование протокола SPICE (Simple Protocol for Independent Computing Environments) созданного как раз для доступа к десктопным VE машинам. В винде уже имеется встроенный виндовый клиент доступа RemoteViewer, но лучше установить свежий родной клиент. Тем более что там же можно взять драйвер редиректа USB.

Для использования SPICE соединения, следует погасить виртуальную машину, после чего в управлении виртуальной машиной PROXMOX, драйвер дисплея виртуальной машины надо переключить в SPICE режим, как показано на картинке. После старта виртуалки можно запускать соединение, либо с помощью виндового Remote Viewer, либо дополнительно установленного VirtViewer – последний работает как то по-стабильней.

З.Ы в процессе поиска решения, нашел самый угарный коммент о том, что чел обнаружил на своем сервере виртуализации установленный netcat6, который и выдавал эту ошибку. После того как он запустил команду “apt-get remove netcat6″ у него отлично заработало novnc. Если кто не понял, то повторять не надо.

Rating: 3.0/10 (20 votes cast)

Rating: -3 (from 3 votes)

Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE, 3.0 out of 10 based on 20 ratings

Теги: proxmox, виртуализация

Источник

22 Jan 2017 | Автор: dd |

Очень странно конечно, но не менее странно, чем отвал сертификата ProxMox в процессе работы.

Rating: 3.1/10 (19 votes cast)

Rating: -3 (from 3 votes)

Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE, 3.1 out of 10 based on 19 ratings

Теги: proxmox, виртуализация

Cloud providers like DigitalOcean, AWS, etc. allow shell access which makes things easier for server owners.

But, what if you cannot access the server via shell?

Here comes the use of “Console Access” that allows direct access to the Droplet.

“Server disconnected code 1006” is an error that shows up when using the “Console Access“. This happens mainly due to firewall restrictions.

At Bobcares, we help server owners to resolve problems with cloud instances as part of our Dedicated Support Services for Web Hosts.

Today, we’ll see the causes for the “Server disconnected code 1006” error in DigitalOcean droplets and how we fix them.

Console Access – pros and cons

Before checking the reasons for the error “Server disconnected (code: 1006)“, let’s have a quick look on the facts about Console access.

It comes handy in situations like:

Remote SSH access becomes unresponsive
Screwed up Droplet configuration files

Here, the console works just like plugging a monitor and keyboard directly to your virtual server. Fortunately, console does not require any additional software. It usually works fine from your browser.

However, it has some demerits too. Console access will be rather slow, compared to a live ssh connection. Also, there is a limitation in the characters that can be used in commands executed via console.

What causes “Server disconnected code 1006” error?

We now know that “Console Access” often helps in unresponsive Droplets.

But, Whats the point if one can’t even access their console?

Let’s now see the reasons that can cause “Console Access” to fail in DigitalOcean panel.

1. Firewall Restrictions

Basically, Console Access option will open a VNC connection to your Droplet.

VNC is a graphical desktop sharing system, where you see the screen of the Droplet on your computer.

It normally uses a random port to connect the browser with the vnc service. Since multiple services are run on each machine that accommodates these Droplets, the port used will be a random one. Usually, it will be in the 5900-7000 range.

Therefore, if the customer’s internet service provider do not allow these port range, it results in the error

"Server disconnected (code: 1006)"

2. Bad Droplet configuration

Again, this error can happen if there are configuration problems with your Droplet.

Here, the Droplet will not be responsive to the Console Access request. And, when you try to access the Droplet, the following error shows up.

Additionally, for the Droplet to work perfectly, the physical server that hosts the droplet should be running fine.

How to fix “Server disconnected code 1006” in DigitalOcean Droplets?

We just saw the reasons for the error “Server disconnected code 1006” in DigitalOcean Droplets.

Now, let’s check how our Dedicated Support Engineers fix this error.

1. Changing Firewall Settings

From our experience in managing DigitalOcean Droplets, we see customers complaining that “Console Access” was working earlier, but not now.

Usually, this happens when customer is connecting from a new network. Therefore, it is clear that the firewall on customer’s network is the root cause.

To confirm this, our Hosting Support Engineers ask customers to check if port 5900 is open in their home network.

And, to fix the error we suggest customers to work with their Internet Service provider to modify the firewall settings. They need to allow the port range for VNC connection. Also, another workaround is to try from an alternate internet connection.

2. Fixing the Droplet

If there are no port restrictions on your network, and still you have problems with Console Access, server needs the fix.

Here, as the first step, we confirm that problem exists only with specific droplet. When other droplets works fine, we can be sure that there are no problems in physical server.

At times, we see Droplets that are completely messed up. In such cases, our Support Engineers quickly rebuild the Droplet from the latest backup. This helps to quickly bring back the websites online.

[Are you experiencing problems connecting to your DigitalOcean Droplet? We can fix Console Access for you.]

Conclusion

In short, during ssh access failure, “Console Access” comes handy in managing DigitalOcean Droplet. But, it often shows the error “Server disconnected code 1006” due to firewall restrictions and wrong Droplet configurations. Today, we’ve seen the top causes for the error and how our Dedicated Support Engineers fix them.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Содержание

Одминский блог
Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE
[SOLVED] Promox 6: problem with noVNC — failed to connect to server
hermelin
starnetwork
«noVNC — failed to connect to server» on Chrome or Edge Chromium, works on Firefox
Elrendhel
Elrendhel
Console -> noVNC — Failed to connect to server
ursus
Moayad
ursus
Moayad
ursus
gdmax
Proxmox VNC «Failed to connect to server»
marciglesias17
Moayad
marciglesias17
Moayad
Psydown
marciglesias17
marciglesias17

Одминский блог

Блог о технологиях, технократии и методиках борьбы с граблями

Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE

Очень странно конечно, но не менее странно, чем отвал сертификата ProxMox в процессе работы.

Источник

hermelin

Active Member

after upgrade to Promox 6, I have probem with noVNC console from webbrowser (Chrome,Firefox tested). After some time I cannot connect noVNC console to VM with error «failed to connect to server». After shutdown and start of VM everything work ok — for some time. Same problem is on VM with linux and Windows. This behaviour is at random for different VM. Some VM with noVNC works, other doesn’t working, at the moment.

Thanks for help

Error in log is

starnetwork

Active Member

same for me:
# pveversion
pve-manager/6.0-6/c71f879f (running kernel: 5.0.18-1-pve)

# pveversion —verbose
proxmox-ve: 6.0-2 (running kernel: 5.0.18-1-pve)
pve-manager: 6.0-6 (running version: 6.0-6/c71f879f)
pve-kernel-5.0: 6.0-6
pve-kernel-helper: 6.0-6
pve-kernel-5.0.18-1-pve: 5.0.18-3
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.2-pve1
ceph-fuse: 14.2.2-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve2
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-7
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-64
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-5
pve-container: 3.0-5
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

Источник

«noVNC — failed to connect to server» on Chrome or Edge Chromium, works on Firefox

Elrendhel

New Member

My first Proxmox VE and it’s working incredibly well! All of my VMs work fine, no problems other than the problem defined below.

My install is fresh on Proxmox CE 7.1-10, and Chrome is my browser of choice.

I have tried the following:

disabled Chrome security for a few minutes (Settings > Security & Privacy > Security > No Protection) and that did not help whatsoever.
I have tried using a different Display such as VMWare, Standard VGA, and VirtIO-GPU, and rebooted each VM after each change to no avail.
I have tried to switch to a different TTY with Ctrl + Alt + F1 or Ctrl + Alt + F2, but this did nothing as well.

This happens for both my Linux VMs (Ubuntu) and my single Windows VM.

Proxmox Retired Staff

seems to be a browser issue in that case (if it works with one but not the others, then likely it’s not an issue on the PVE end).

maybe you have some add-ons on your chrome/edge that are messing with it? have you tried clearing browser cache and/or using incognito mode without extensions?

it’s also possible that some antivirus software don’t like your browser making external connections (various internet security etc. software can block this)

Best regards,
Oguz

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Elrendhel

New Member

Thank you for taking the time to assist me! I would entirely agree that it is something to do with the way that Chrome (and by extension Edge Chromium) operates. Specifically, I think it’s the way that they treat security via the HTTPS protocol.

Yes, I did in fact try several other strategies but neglected to site them, my bad:

I have deleted all browser-cache and windows temp file-cache, same problem.
I have disabled all «extensions», same problem.
I have tried incognito mode with no extensions, same problem.
I did try to import the self-signed certificate into Chrome, but it didn’t get rid of the HTTPS error. Of course same problem.
I created a whole new windows profile with no other programs set to autoload, and all AV disabled and all of the above. Of course same problem.

I still think that if I fix the HTTPS issue, Chrome (and Chromium based Edge) will start working properly to allow noVNC to operate.

Is there a better way to get the HTTPS certificate issue fixed?

Also, I would point out a discrepancy in the way that Proxmox is reporting the problem. While the top of the noVNC screen shouts «Can’t connect to server» (screenshot attached), when I look at the error message in the Task Log, it says «Connection Timed Out» (screenshot attached as well), if that helps.

Thank you again for your assistance in this endeavor, it is greatly appreciated!

Источник

Console -> noVNC — Failed to connect to server

ursus

New Member

I have the newest version of ProxMox installed (7.0-14+1) — I did not upgrade but have installed all updated packages. I am getting the dreaded noVNC error in all the browsers that I have (I have tried Mac: Safari, Chrome and Firefox. Windows: Chrome and Firefix). This is not normally a problem as I can just SSH to the machines and work that way, no real need for the console. I would now like to install a new Debian VM and cannot connect to install — major problem! I have tried to reboot the Proxmox server i.e. restarted the Hardware but even this did not help. I have read in the forums that something similar happened if you updated from 5 to 6 without doing some preliminary steps, but I started with 7.

Thank you for any help given
ursus

Moayad

Proxmox Staff Member

Are you mean that you installed the updated packages manually or using apt?

Could you please post the output of pveversion -v . However, did you try to renew the certificate for your PVE with pvecm updatecerts -f command?

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

ursus

New Member

Yes, I installed and updated the packages manually.

here is the output from: pveversion -v

and the result of pvecm updatecerts -f:

and the updatecerts command did not change my situation!

Moayad

Proxmox Staff Member

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

ursus

New Member

gdmax

New Member

HI guys,
I have the same issue with the new Ver. 7.1-10 especially with FreeNas11.3 / TrueNas12u8 VM ( i have tried both )
I noticed that after adding the PCI Device Passthrough of the LSI raid card on the Truenas VM Hardware section the VNC won’t start, if i remove the PCI Device , the Truenass boot o.k but i won’t see my drives.

before upgrading to the new Proxmox Ver ( new install from scratch ) i had Proxmox 6.3.3 Ver with Freenas 11.3 working grate for a Year+ now
even though my Prec h710 Raid card isn’t on IT mode ( i just configured each of the 4 SAS/SATA 2 TB drives as Raid 0 on different Virtual group for each Drive )

Specs: Del T320 / 96 GB ram
CPU: 20 x Intel(R) Xeon(R) CPU E5-2470 v2 @ 2.40GHz (1 Socket )
Kernel Version : Linux 5.13.19-4-pve #1 SMP PVE 5.13.19-8 (Mon, 31 Jan 2022 10:09:37 +0100)
PVE Manager Version: pve-manager/7.1-10/6ddebafe

needless to say the my CPU support IOMMU
All VTd on Bios are enabled

Источник

Proxmox VNC «Failed to connect to server»

marciglesias17

Member

I have one of my nodes in Cluster with 6.1.17 version but VNC no connect.

Moayad

Proxmox Staff Member

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

marciglesias17

Member

Moayad

Proxmox Staff Member

Please post output of command: pveversion -v

Also check if there any firewall or antivirus that not allow TLS traffic

Best regards,
Moayad

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Psydown

New Member

marciglesias17

Member

marciglesias17

Member

Please post output of command: pveversion -v

Also check if there any firewall or antivirus that not allow TLS traffic

pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Источник

Hello,

I am new to the forum and proxmox, currently i am facing an issue when connecting to the console.

Everytime i try to connect to the console i get the following error message: «Server disconnected (code: 1006)»

Any help is greatly appreciated.

What browser/os/version do you use?

Hi, same issue here, but only on one node in cluster.

Test with newest FF, Opera, IE and Chrome.

error msg in log:

Code:

TASK ERROR: command '/bin/nc -l -p 5901 -w 10 -c '/usr/bin/ssh -T -o  BatchMode=yes 217.*.*.* /usr/sbin/qm vncproxy 5402 2>/dev/null''  failed: exit code 255
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/bin/ssh -T -o  BatchMode=yes 217.*.*.* /usr/sbin/qm vncproxy 5131 2>/dev/null''  failed: exit code 255

regards

Hi, same issue here, but only on one node in cluster.

That IP address looks strange «217.*.*.*» Why does it conatin ‘*’?

Hi, we can post our IP if you would, we have only comment it on this post^^.

regards

Hi, we can post our IP if you would, we have only comment it on this post^^.

Next time, please mention that you manually modified the log output …

ok, i wouldn´t modify it in next time, but do you have a workarround for this issue?

regards

but do you have a workarround for this issue?

no idea, sorry. Please try to debug by running those command on the command line …

Hi, without /dev/null:

Code:

'/bin/nc -l -p 5900 -w 10 -c '/usr/bin/ssh -T -o BatchMode=yes 217.69.254.69 /usr/sbin/qm vncproxy 5131
-bash: /bin/nc -l -p 5900 -w 10 -c /usr/bin/ssh: Datei oder Verzeichnis nicht gefunden

Code:

/bin/nc -l -p 5900 -w 10 -c /usr/bin/ssh -T -o BatchMode=yes 217.69.254.69 /usr/sbin/qm vncproxy 5131
BatchMode=yes: forward host lookup failed: Host name lookup failure

Make sure you quote the command currectly, and verify what is missing /bin/nc or /usr/bin/sh ?

Hi, i have edit the post, with correct command.

regards

Last edited: Oct 16, 2014

Hi all,

any ideas to fix it?

regards

Hi all, we have test lookup hostname, and reverse lookup and ping hostname … all working fine. what can we do do solve this error?

please help. very thanks and bet regards

Hi all, we have found a solution for this problem.

you must clean /root/.ssh/know_hosts on node and cluster. after this you connect via ssh to node and cluster and have new keys. after this the vnc console works fine, without 1006 error.

regards

Hi all, we have found a solution for this problem.

you must clean /root/.ssh/know_hosts on node and cluster. after this you connect via ssh to node and cluster and have new keys. after this the vnc console works fine, without 1006 error.

regards

Hi,

Can you give any more detail on what you did? I emptied known_hosts on the nodes, but what else needs to be done?

Thanks!

After more investigation, I found that netcat6 was installed on my servers and caused this error. I ran «apt-get remove netcat6» and novnc started working immediately afterwards.

For future time travelers:

If you want to see the console from a vm on another node in your cluster and you get error 1006 in your browser console your issue might be this:

Try to ssh from the node which throws an error to the desired target node.

node01 -> node02 (example)

You may get an error similar to this one:

Code:

Warning: the ECDSA host key for 'XXXX' differs from the key for the IP address 'X.X.X:X'
Offending key for IP in /etc/ssh/ssh_known_hosts:4
Matching host key in /root/.ssh/known_hosts:1
Are you sure you want to continue connecting (yes/no)?

To fix this error, remove the entries of the broken target node in the following files (in this sample all entries about node02):

Code:

/etc/pve/priv/known_hosts
/etc/ssh/ssh_known_hosts
/root/.ssh/known_hosts

After this ssh from node01 to node02 via command line. You should get this info:

Code:

The authenticity of host 'node02 (X.X.X.X)' can't be established.
ECDSA key fingerprint is SHA256:XXXX
Are you sure you want to continue connecting (yes/no)?

Accept with yes. Log out of the remote shell again and try to ssh into node02 (from node01) again just to check that you’ll be grated access without any further question or error.

You should now be able to use your cluster as expected again.

Hello,

I am new to the forum and proxmox, currently i am facing an issue when connecting to the console.

Everytime i try to connect to the console i get the following error message: «Server disconnected (code: 1006)»

Any help is greatly appreciated.

the same error after testing how 3 browsers worked with firefox. lucky

For what its worth, i experienced the same error-code on my cluster (1006) but looking in the error on the webUI mentions of

Code:

LC_PVE_TICKET not set, VNC proxy without password is forbidden

Examining nodes i found that known_hosts were on their own ( /root/.ssh/known_hosts, /etc/ssh/ssh_known_hosts), instead of being sym-linked to /etc/pve/priv/known_hosts

Another observation : seems that the preference/default of a ssh-dsa key has changed to ecdsa-sha2-nistp256.

So in my setup i have used ansible to correct/inject both the ssh-dsa aswell as the ecdsa-sha2-nistp256 — keys into the known hosts located at /etc/pve/priv/known_hosts

Since then its all cool and no issues anymore.

I had this problem and managed to fix it by

clicking on the server, going to DNS and putting my gateways address in the DNS server 1

after that it installed fine.

But why?

Using another VNC client I can connect to VM.

In the browser console:

Data URI scheme cursor supported
util.js:214 >> RFB.constructor
util.js:214 >> Display.constructor
util.js:214 User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36
util.js:214 Browser: webkit 537.36
util.js:214 Setting viewport to full display region
util.js:214 << Display.constructor
util.js:216 Using native WebSockets
util.js:214 >> Keyboard.allKeysUp
util.js:214 << Keyboard.allKeysUp
util.js:214 Setting viewport to full display region
util.js:218  Msg: noVNC ready: native WebSockets, canvas rendering
util.js:214 << RFB.constructor
util.js:214 >> Keyboard.allKeysUp
util.js:214 << Keyboard.allKeysUp
util.js:218 
util.js:214 >> RFB.connect
util.js:216 connecting to ws://192.168.1.193:8080/
util.js:216 Detected binaryType support in WebSockets
util.js:214 << RFB.connect
util.js:214 >> WebSock.onopen
util.js:216 Server choose sub-protocol: binary
util.js:218  Msg: Starting VNC handshake
util.js:214 << WebSock.onopen
util.js:216 Server ProtocolVersion: 003.008
util.js:218  Msg: Sent ProtocolVersion: 003.008
util.js:214 >> WebSock.onclose
util.js:218 WebSocket on-close event
util.js:214 >> Keyboard.allKeysUp
util.js:214 << Keyboard.allKeysUp
util.js:220  Msg: Server disconnected (code: 1006)Util.Error @ util.js:220RFB._updateState @ rfb.js:470RFB._fail @ rfb.js:540(anonymous function) @ rfb.js:208(anonymous function) @ websock.js:314
util.js:214 << WebSock.onclose
util.js:214 >> Keyboard.allKeysUp
util.js:214 << Keyboard.allKeysUp
util.js:218

On the server:

./launch.sh --listen 8080 --vnc 192.168.1.193:5901 --web /var/www/htdocs/app/webroot/noVNC/
Warning: could not find self.pem
Using local websockify at /var/www/htdocs/app/webroot/noVNC/utils/websockify/run
Starting webserver and WebSockets proxy on port 8080
WebSocket server settings:
  - Listen on :8080
  - Flash security policy server
  - Web server. Web root: /var/www/htdocs/app/webroot/noVNC
  - No SSL/TLS support (no cert file)
  - proxying from :8080 to 192.168.1.193:5901


Navigate to this URL:

    http://bibidibuppi:8080/vnc.html?host=crististore&port=8080

Press Ctrl-C to exit


robert - - [18/Nov/2015 17:36:20] "GET / HTTP/1.1" 101 -
robert - - [18/Nov/2015 17:36:20] 192.168.1.107: Plain non-SSL (ws://) WebSocket connection
robert - - [18/Nov/2015 17:36:20] 192.168.1.107: Version hybi-13, base64: 'False'
robert - - [18/Nov/2015 17:36:20] connecting to: 127.0.0.1:5901
Reaping zombies, active child count is 0
Ignoring interrupted syscall

And then nothing happens. Actually I get the Server disconnected (code: 1006) in the browser console.

При входе в IPMI вы можете столкнуться с разными ошибками. Рассказываем, что делать в каждом случае.

Поля «логин» и «пароль» не заполняются автоматически
Ошибка «Server disconnected: (code: 1006)»
Ошибка «IPMI URL … of selected server is not available»

Поля «логин» и «пароль» не заполняются автоматически

Обычно логин и пароль можно не вводить вручную. Они заполнятся автоматически, если кликнуть на поле, а затем на подходящую кнопку в углу экрана.

Если автозаполнение не сработало, попробуйте ввести данные вручную. Логин и пароль вы найдёте в DCImanager — наведите курсор на иконку монитора и увидите данные для входа.

Даже если получилось войти, введя данные вручную, напишите в техническую поддержку — мы сделаем так, чтобы автозаполнение полей заработало. Если войти не вышло, тоже обратитесь в поддержку — мы наладим подключение.

Такая ошибка появляется, когда с IPMI открыты две сессии сразу — например, если подключаться одновременно с двух устройств или из разных вкладок в браузере.

Увидев ошибку, попробуйте сделать поочерёдно четыре вещи:

Проверьте, нет ли двух открытых вкладок с IPMI. Если есть, закройте одну и работайте с IPMI из другой
Закройте текущий браузер, откройте другой и подключитесь к IPMI через него
Очистите cookies браузера и подключитесь к IPMI
Подключитесь IPMI с другого устройства — например, с мобильного

Если ни один из способов не помог, напишите в техническую поддержку — мы сделаем так, чтобы IPMI снова заработала. Обязательно укажите, что проделали все шаги из статьи: так мы сразу поймём, в чём дело, и не будем просить вас подключаться разными способами.

Ошибка «IPMI URL … of selected server is not available»

Такая ошибка возникает при сбоях сервера или когда в локации проходят аварийные либо запланированные работы.

Увидев эту ошибку, напишите в техническую поддержку — мы наладим доступ в IPMI. В свой текст скопируйте описание ошибки или сделайте скриншот экрана: так мы сразу поймём, что случилось.

17.12.2016, 09:13

#1

Senior Member

VNC SSL и нашумевший код 1006

А теперь вернемся к нашему любимому VNC SSL под соусом 1006 =)
Сколько уже раз этот вопрос подымался и ни разу четкого решения ему не было.

! Да, сто раз уже говорилось что нужно в manager.crt /manager.key вбить свой сертификат что бы все работало, прописано, но «_но» всегда всплывает.
! И да, в manager.crt прописан bundle (сам сертификат и CA cert).

Стоит панель 5.86.0 KVM. Сертификат уже поменяли 3 раза, уже и за $$$$ выкупили, толку не много.
Поработало неделю и вновь выпадает в 1006. Особенно в

Chrome (в Safari все ОК). На разных ПК/Mac тоже самое, в Хроме 1006.
Дебажить WebSocket нереально. Точно что нужно гадалку в ДЦ нанять для таких ситуаций.

Последний раз редактировалось Neolo; 17.12.2016 в 09:17.
20.12.2016, 14:30

#2

ISPsystem team

Напишите в центр поддержки, посмотрим в чем дело. Четкого решения вы на форуме не получите, потому что чтобы дать четкий ответ, надо изучить ситуацию «на месте».
20.12.2016, 23:43

#3

Senior Member

Я хочу узнать у кого еще код 1006 периодически появляется без причины, но в разных браузерах.

proxmox:troubleshooting:nonvc_fails_to_connect_with_server_disconnected_code:1006

Proxmox — Troubleshooting — noNVC fails to connect with Server disconnected (code: 1006)

Trying to connect to a console within Proxmox returns the following error message: Server disconnected (code: 1006).

TASK ERROR: command '/usr/bin/termproxy 5901 --path /nodes/pve --perm Sys.Console -- /bin/login -f root' failed: exit code 1

Regenerate Certificates

SSH into the Proxmox host.

pvecm updatecerts --force
systemctl restart pvedaemon.service
systemctl restart pveproxy.service

NOTE: The certificates are out of sync, so regenerate them.

Revert to default SSL configuration

rm -rf /etc/pve/pve-root-ca.pem
rm -rf /etc/pve/priv/pve-root-ca.key
rm -rf /etc/pve/nodes/pve/pve-ssl.pem
rm -rf /etc/pve/nodes/pve/pve-ssl.key
rm /etc/pve/pve-root-ca.pem /etc/pve/priv/pve-root-ca.key
 
pvecm updatecerts -f
systemctl restart pveproxy

Check Logs

cat /var/log/daemon.log | grep -e pveproxy -e pvedaemon

returns:

...
Jul 21 09:11:48 pve pvedaemon[191274]: <root@pam> successful auth for user 'root@pam'
Jul 21 09:11:55 pve pvedaemon[192394]: starting termproxy UPID:pve:0002EF8A:002A3230:60F7D6CB:vncshell::root@pam:
Jul 21 09:11:55 pve pvedaemon[191276]: <root@pam> starting task UPID:pve:0002EF8A:002A3230:60F7D6CB:vncshell::root@pam:
Jul 21 09:12:05 pve pvedaemon[192394]: command '/usr/bin/termproxy 5900 --path /nodes/pve --perm Sys.Console -- /bin/login -f root' failed: exit code 1
Jul 21 09:12:05 pve pvedaemon[191276]: <root@pam> end task UPID:pve:0002EF8A:002A3230:60F7D6CB:vncshell::root@pam: command '/usr/bin/termproxy 5900 --path /nodes/pve --perm Sys.Console -- /bin/login -f root' failed: exit code 1
Jul 21 09:12:14 pve pvedaemon[192565]: starting vnc proxy UPID:pve:0002F035:002A39AA:60F7D6DE:vncproxy:102:root@pam:
Jul 21 09:12:14 pve pvedaemon[191276]: <root@pam> starting task UPID:pve:0002F035:002A39AA:60F7D6DE:vncproxy:102:root@pam:
Jul 21 09:12:29 pve pvedaemon[191276]: <root@pam> end task UPID:pve:0002F035:002A39AA:60F7D6DE:vncproxy:102:root@pam: OK
Jul 21 09:12:33 pve pvedaemon[192703]: starting lxc termproxy UPID:pve:0002F0BF:002A4103:60F7D6F1:vncproxy:202:root@pam:
Jul 21 09:12:33 pve pvedaemon[191274]: <root@pam> starting task UPID:pve:0002F0BF:002A4103:60F7D6F1:vncproxy:202:root@pam:
Jul 21 09:12:33 pve pvedaemon[191276]: <root@pam> successful auth for user 'root@pam'
...

NOTE: The vncproxy is failing.

Check if the websockify service is running

ps aux |grep websoc

NOTE: The socat package needs to be installed on the server.

Another Approach

Obtain a certificate to allow the Proxmox web interface to work over https.

Then, add this certificate to the list of trusted certificates on the remote PC being used to access Proxmox.

openssl s_client -showcerts -connect 192.168.1.95:8006 /dev/null | openssl x509 -outform PEM > pve.pem

NOTE: Where:

192.168.1.95:8006 is the address of the web interface of the Proxmox hypervisor.
pve.pem is the output file of the certificate.

Then just add this certificate and set the rights to it Always trust.

Reload the Proxmox web page and access to the console should work.

Источник

Well, if you are having problem with NoVNC not working on your proxmox and has been ignoring it up until now, its time to make it work. NoVNC basically uses web socket and html5 to allow you to remote access your virtual machine. So make sure you use a browser such as Chrome instead of Safari which has a full compatibility of web socket implementation on the browser. If not, you will most likely get yourself an error such as this,

TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 100 2>/dev/null'' failed: exit code 1

Due to compatibility issue, Proxmox NoVNC might not work with the default install. All you need to do is to find out which NoVNC works for your current Proxmox installation and down/upgrade it! And for me, the version NoVNC 0.47 works for me so i downgraded it from 0.53 by doing the following,

wget http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/novnc-pve_0.4-7_amd64.deb
dpkg -i novnc-pve_0.4-7_amd64.deb

And it will do the rest, and if you would like try other version, just head down to the following link

http://download1.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/

to get all the binary you need.

Источник

Go to Proxmox

New VM with noVNC «Failed to connect to server» error

Hello,

New to Proxmox which is installed on a former daily driver. Intel i5-4460 quad core with 16 GB of RAM.

Attempted to start my first VM using all 4 cores and 8 GB RAM using an Ubuntu ISO. I first tried 20.04 Server and then 18.04 server. No dice.

Receiving a «Failed to connect to server» message with noVNC.

Syslog: Mar 16 18:56:37 johnny5 pvedaemon[1567]: <root@pam> end task UPID:johnny5:00001610:0001BACB:605145AB:vncproxy:100:root@pam: connection timed out

pveversion:

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: 0.8.35+pve1
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
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

VM config:

root@johnny5:/etc/pve# qm config 100
agent: 1
boot: order=scsi0;ide2;net0
cores: 4
ide2: system_storage_ssd:iso/ubuntu-18.04.5-live-server-amd64.iso,media=cdrom
memory: 8192
name: test
net0: virtio=CE:24:36:BF:82:FB,bridge=vmbr0
numa: 0
ostype: l26
scsi0: nvme_pool:vm-100-disk-0,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=0d9c625c-4eca-454f-ac38-0a62310ca501
sockets: 1
vmgenid: 6c8181c1-9923-4edf-a0e5-f550fc58a6d8

I have no production or any important information on this at all at the moment. Still in the learning phase before I truly start building this puppy out.

Источник

oguz

Proxmox Retired Staff

oguz

Proxmox Retired Staff

Console Access – pros and cons

What causes “Server disconnected code 1006” error?

1. Firewall Restrictions

2. Bad Droplet configuration

How to fix “Server disconnected code 1006” in DigitalOcean Droplets?

1. Changing Firewall Settings

2. Fixing the Droplet

Conclusion

PREVENT YOUR SERVER FROM CRASHING!

Одминский блог

Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE

hermelin

Active Member

starnetwork

Active Member

«noVNC — failed to connect to server» on Chrome or Edge Chromium, works on Firefox

Elrendhel

New Member

Proxmox Retired Staff

Elrendhel

New Member

Console -> noVNC — Failed to connect to server

ursus

New Member

Moayad

Proxmox Staff Member

ursus

New Member

Moayad

Proxmox Staff Member

ursus

New Member

gdmax

New Member

Proxmox VNC «Failed to connect to server»

marciglesias17

Member

Moayad

Proxmox Staff Member

marciglesias17

Member

Moayad

Proxmox Staff Member

Psydown

New Member

marciglesias17

Member

marciglesias17

Member

Поля «логин» и «пароль» не заполняются автоматически

Ошибка «IPMI URL … of selected server is not available»

<img decoding="async" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" /> VNC SSL и нашумевший код 1006

<img decoding="async" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

Table of Contents

Proxmox — Troubleshooting — noNVC fails to connect with Server disconnected (code: 1006)

Regenerate Certificates

Revert to default SSL configuration

Check Logs

Check if the websockify service is running

Another Approach

VNC SSL и нашумевший код 1006