Содержание
- Одминский блог
- Ошибка 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 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. Если кто не понял, то повторять не надо.
Источник
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.
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.
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
Источник
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.1/10 (19 votes cast)
Rating: -3 (from 3 votes)
Ошибка 1006 noVNC соединения к виртуальной машине Proxmox VE, 3.1 out of 10 based on 19 ratings
Теги: proxmox, виртуализация
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc viewer, the connection will established.
Here is a Debug log
RFB.constructor util.js:38:55
Display.constructor util.js:38:55
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0 util.js:38:55
Browser: gecko 19 util.js:38:55
Setting viewport to full display region util.js:38:55
<< Display.constructor util.js:38:55
Keyboard.allKeysUp util.js:38:55
<< Keyboard.allKeysUp util.js:38:55
Using native WebSockets, render mode: canvas rendering util.js:40:55
<< RFB.constructor util.js:38:55
New state ‘connecting’, was ». util.js:38:55
RFB.connect util.js:38:55
connecting to ws://live1.power-dog.eu:1492/websockify util.js:40:55
Detected binaryType support in WebSockets util.js:40:55
<< RFB.connect util.js:38:55
GEThttp://live1.power-dog.eu:1492/websockify
Firefox kann keine Verbindung zu dem Server unter ws://live1.power-dog.eu:1492/websockify aufbauen. websock.js:278:30
WebSock.onerror: [object Event] util.js:38:55
WebSocket on-error event util.js:42:55
<< WebSock.onerror: [object Event] util.js:38:55
WebSock.onclose util.js:38:55
WebSocket on-close event util.js:42:55
Failed when connecting: Failed to connect to server( (code: 1006)) util.js:44:55
New state ‘disconnecting’, was ‘connecting’. util.js:38:55
RFB.disconnect util.js:38:55
Keyboard.allKeysUp util.js:38:55
<< Keyboard.allKeysUp util.js:38:55
Encoding stats for this connection: util.js:40:55
Encoding stats since page load: util.js:40:55
COPYRECT: 0 rects util.js:40:55
TIGHT: 0 rects util.js:40:55
TIGHT_PNG: 0 rects util.js:40:55
HEXTILE: 0 rects util.js:40:55
RRE: 0 rects util.js:40:55
RAW: 0 rects util.js:40:55
JPEG_quality_med: 0 rects util.js:40:55
compress_hi: 0 rects util.js:40:55
DesktopSize: 0 rects util.js:40:55
last_rect: 0 rects util.js:40:55
Cursor: 0 rects util.js:40:55
QEMUExtendedKeyEvent: 0 rects util.js:40:55
ExtendedDesktopSize: 0 rects util.js:40:55
xvp: 0 rects util.js:40:55
Fence: 0 rects util.js:40:55
ContinuousUpdates: 0 rects util.js:40:55
<< RFB.disconnect util.js:38:55
New state ‘disconnected’, was ‘disconnecting’. util.js:38:55
Clearing disconnect timer util.js:38:55
<< WebSock.onclose util.js:38:55
Somebody know this issue?
Thanks for helping
Hi,
Do you have a WebSocket proxy up and running on your server? noVNC requires a WebSocket to TCP proxy in order to work.
Some VNC servers like QEMU and libvncserver come with a built in proxy, otherwise you can have a look at our sister-project websockify.
Hi,
yes we use libvncserver. If the connection is good enough, i can connect to the VNC Server. Only by a bad connection i cant connect via novnc
I’m afraid the log only shows that the browser fails to connect. As such there isn’t much we can do. It’s either an issue in Firefox, or libvncserver, or that your network is simply not working well enough to establish a connection.
I’d advise to check the network tab in Firefox’ developer tools. It might give you more details. Also check the logs for libvncserver. Other than that I’m afraid I’ll have to ask you to fill a bug with either of those projects.
I think the Problem ist a connection timeout. Now i have tested with guacamole an with RealVNC Client and it works perfect. I can connect to the Clients which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc viewer, the connection will established.
Here is a Debug log
RFB.constructor util.js:38:55
Display.constructor util.js:38:55
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0 util.js:38:55
Browser: gecko 19 util.js:38:55
Setting viewport to full display region util.js:38:55
<< Display.constructor util.js:38:55
Keyboard.allKeysUp util.js:38:55
<< Keyboard.allKeysUp util.js:38:55
Using native WebSockets, render mode: canvas rendering util.js:40:55
<< RFB.constructor util.js:38:55
New state ‘connecting’, was ». util.js:38:55
RFB.connect util.js:38:55
connecting to ws://live1.power-dog.eu:1492/websockify util.js:40:55
Detected binaryType support in WebSockets util.js:40:55
<< RFB.connect util.js:38:55
GEThttp://live1.power-dog.eu:1492/websockify
Firefox kann keine Verbindung zu dem Server unter ws://live1.power-dog.eu:1492/websockify aufbauen. websock.js:278:30
WebSock.onerror: [object Event] util.js:38:55
WebSocket on-error event util.js:42:55
<< WebSock.onerror: [object Event] util.js:38:55
WebSock.onclose util.js:38:55
WebSocket on-close event util.js:42:55
Failed when connecting: Failed to connect to server( (code: 1006)) util.js:44:55
New state ‘disconnecting’, was ‘connecting’. util.js:38:55
RFB.disconnect util.js:38:55
Keyboard.allKeysUp util.js:38:55
<< Keyboard.allKeysUp util.js:38:55
Encoding stats for this connection: util.js:40:55
Encoding stats since page load: util.js:40:55
COPYRECT: 0 rects util.js:40:55
TIGHT: 0 rects util.js:40:55
TIGHT_PNG: 0 rects util.js:40:55
HEXTILE: 0 rects util.js:40:55
RRE: 0 rects util.js:40:55
RAW: 0 rects util.js:40:55
JPEG_quality_med: 0 rects util.js:40:55
compress_hi: 0 rects util.js:40:55
DesktopSize: 0 rects util.js:40:55
last_rect: 0 rects util.js:40:55
Cursor: 0 rects util.js:40:55
QEMUExtendedKeyEvent: 0 rects util.js:40:55
ExtendedDesktopSize: 0 rects util.js:40:55
xvp: 0 rects util.js:40:55
Fence: 0 rects util.js:40:55
ContinuousUpdates: 0 rects util.js:40:55
<< RFB.disconnect util.js:38:55
New state ‘disconnected’, was ‘disconnecting’. util.js:38:55
Clearing disconnect timer util.js:38:55
<< WebSock.onclose util.js:38:55
Somebody know this issue?
Thanks for helping
Hi,
Do you have a WebSocket proxy up and running on your server? noVNC requires a WebSocket to TCP proxy in order to work.
Some VNC servers like QEMU and libvncserver come with a built in proxy, otherwise you can have a look at our sister-project websockify.
Hi,
yes we use libvncserver. If the connection is good enough, i can connect to the VNC Server. Only by a bad connection i cant connect via novnc
I’m afraid the log only shows that the browser fails to connect. As such there isn’t much we can do. It’s either an issue in Firefox, or libvncserver, or that your network is simply not working well enough to establish a connection.
I’d advise to check the network tab in Firefox’ developer tools. It might give you more details. Also check the logs for libvncserver. Other than that I’m afraid I’ll have to ask you to fill a bug with either of those projects.
I think the Problem ist a connection timeout. Now i have tested with guacamole an with RealVNC Client and it works perfect. I can connect to the Clients which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
zwick88 opened this issue
Nov 5, 2019
· 7 comments
Closed
Failed to connect to server
#1315
zwick88 opened this issue
Nov 5, 2019
· 7 comments
Comments
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc client or guacamole, the connection will established.
I think the Problem ist a connection timeout.
I can connect to the Clients with RealVNC or Guacamole which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
I’m afraid we have no control over such things. It is entirely up to the browser. What does your browser console say?
Can you connect directly when you are in the same location?
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc client or guacamole, the connection will established.
I think the Problem ist a connection timeout.I can connect to the Clients with RealVNC or Guacamole which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
Of course I can connect if I’m local, otherwise I can not connect with Guacamole or a VNC client
Can you also connect with noVNC when you are local?
i cannt connect to vncserver by firefox, ie or chrome when i use websockify-other instead of websockify, but i can do that by using v1.1.0. what’s wrong?
I’m afraid this is some browser issue and it isn’t much we can do about it. Please report this to Firefox and hopefully they can help out.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
zwick88 opened this issue
Nov 5, 2019
· 7 comments
Closed
Failed to connect to server
#1315
zwick88 opened this issue
Nov 5, 2019
· 7 comments
Comments
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc client or guacamole, the connection will established.
I think the Problem ist a connection timeout.
I can connect to the Clients with RealVNC or Guacamole which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
I’m afraid we have no control over such things. It is entirely up to the browser. What does your browser console say?
Can you connect directly when you are in the same location?
Hi there,
i’m using a lot of embedded Linux devices for several jobs. Some devices are connected via LTE Mobile Routers and other devices only with 3G or 2G.
Now my problem is that i could not connect to the server via noVnc. Error message: Failed to connect to server. When i try to connect with realvnc client or guacamole, the connection will established.
I think the Problem ist a connection timeout.I can connect to the Clients with RealVNC or Guacamole which with noVNC dosnt work.
Is it Possible that a timeout val is the Problem? Can someone give me a help to find the right line in the code?
Of course I can connect if I’m local, otherwise I can not connect with Guacamole or a VNC client
Can you also connect with noVNC when you are local?
i cannt connect to vncserver by firefox, ie or chrome when i use websockify-other instead of websockify, but i can do that by using v1.1.0. what’s wrong?
I’m afraid this is some browser issue and it isn’t much we can do about it. Please report this to Firefox and hopefully they can help out.