If you can, start the container without VNC and execute docker exec -it container_name /bin/bash:
- gosu deconz tigervncserver -list ‘:*’ -cleanstale
- gosu deconz tigervncserver -SecurityTypes VncAuth,TLSVnc “:5900”
Result of first statement:
tigervncserver: Option ‘:*’: Unrecognized!
Of the second:
tigervncserver: Option “:5900”: Unrecognized!
gosu deconz tigervncserver -list :* -cleanstale
gosu deconz tigervncserver -SecurityTypes VncAuth,TLSVnc :0
The first statment does not return any server session.
The second one returns:
Killing Xtigervnc process ID 1738... which seems to be deadlocked. Using SIGKILL!
=================== tail /home/deconz/.vnc/0cf5526769ed:5900.log ===================
====================================================================================
tigervncserver: /usr/bin/Xtigervnc did not start up, please look into '/home/deconz/.vnc/0cf5526769ed:5900.log' to determine the reason! -1
I have checked the log file and it is also empty.
I had exactly this problem whilst trying to diagnose something else, it was tied to an old version of libseccomp2
try option 2 here FAQ - LinuxServer.io then restart docker
may help
That solved my problem 
. Great, thank you very much! 
But also many thanks to Philippe and Dennis for your support!
Best regards,
Jörg
1 Like
I have this same problem trying to upgrade from 2.14.01 to 2.15.03, but I am running Docker on a Synology NAS using the GUI. If revert to my backup of 2.14.01, all is well again. Is anyone able to give me instructions to solve this problem? I looked at @cleggton solution but I don’t know how to implement it. Logs are below. Thanks!
[deconzcommunity/deconz] Starting deCONZ...
stdout
01:47:38
[deconzcommunity/deconz] Current deCONZ version: 2.15.03
stdout
01:47:38
[deconzcommunity/deconz] Web UI port: 8582
stdout
01:47:38
[deconzcommunity/deconz] Websockets port: 443
stdout
01:47:38
[deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --http-port=8582 --ws-port=443
stdout
01:47:38
[deconzcommunity/deconz] Modifying user and group ID
stdout
01:47:38
usermod: no changes
stdout
01:47:39
[deconzcommunity/deconz] Checking device group ID
stdout
01:47:39
[deconzcommunity/deconz] VNC port: 5900
stdout
01:47:39
hostname: Name or service not known
stdout
01:47:39
tigervncserver: Could not acquire fully qualified host name of this machine.
stdout
01:47:39
hostname: Name or service not known
stdout
01:47:39
tigervncserver: Could not acquire fully qualified host name of this machine.
stdout
01:47:39
hostname: Name or service not known
stdout
01:47:39
tigervncserver: Could not acquire fully qualified host name of this machine.
stdout
01:47:40
WebSocket server settings:
stdout
01:47:40
- Listen on :6080
stdout
01:47:40
- Web server. Web root: /usr/share/novnc
stdout
01:47:40
- SSL/TLS support
stdout
01:47:40
- Backgrounding (daemon)
stdout
01:47:40
[deconzcommunity/deconz] NOVNC port: 6080
stdout
01:47:40
qt.qpa.xcb: could not connect to display :0
stdout
01:47:40
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
stdout
01:47:40
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
stdout
01:47:40
stdout
01:47:40
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
stdout
01:47:40
stdout
01:48:41
[deconzcommunity/deconz] Starting deCONZ...
stdout
01:48:41
I’m not familiar with Synology Nas.
The first step would be to make sure your Nas has the most up to date firmware and docker package.
I am not using DSM 7, but I have the latest version for DSM 6 (6.2.4-25556 Update 5). DSM 7 breaks support for usb devices like the Conbee II…
As a temporary workaround, I have set the environment variable “deconz_vnc_mode” to 0. This isn’t ideal, of course, because I lose VNC access. The variable “deconz_vnc_display” is also set to 0 - does anyone have any tips as to what I could do to solve this issue?
deconz (2.16.01) runs well within docker on a synology NAS (running DSM7.0) without any problem (VNC works well). In the past when I used 2.15.03, I had the following configuration:
For DSM7.0, Conbee II works fine if you load the usbserial kernel module which is still available:
modprobe usbserial
Hope it helps
Error Is stil on 2.17.01
Any fix or news?
root@deCONZ-2:/# gosu deconz tigervncserver -list :* -cleanstale
hostname: Name or service not known
tigervncserver: Could not acquire fully qualified host name of this machine.
root@deCONZ-2:/# gosu deconz tigervncserver -SecurityTypes VncAuth,TLSVnc :0
hostname: Name or service not known
tigervncserver: Could not acquire fully qualified host name of this machine.
Can you check if you have configured the hostname correctly?
Also check https://github.com/deconz-community/deconz-docker/issues/110
Finally! This is what solved the issue for me too. Restored from a phoscon backup successfully afterwards. Thank you!
i changed my account. I repost the solution for your problem:
You have to create the container in the ssl terminal and not in the synology docker interface.
docker run -d
–name=deconz
–restart=always
-p 80:80
-p 443:443
-v /etc/localtime:/etc/localtime:ro
-v /opt/deconz:/opt/deCONZ
–device=/dev/ttyUSB0
deconzcommunity/deconz
how to enable vnc mode and change usb settings are found on the deconz docker page
1 Like