Namru

Thank you very much spall, it solves the issue for me!

deletion of cookies and other website data doesn't help for me. Docker Logs shows after VNC paramters the following output: (EE) Fatal server error: (EE) Unrecognized option: - (EE) 2022-11-22 16:10:25,301 DEBG 'start' stdout output: Openbox-Message: Failed to open the display from the DISPLAY environment variable. 2022-11-22 16:10:25,451 DEBG 'start' stderr output: WebSocket server settings: - Listen on :6080 2022-11-22 16:10:25,451 DEBG 'start' stderr output: - Web server. Web root: /usr/share/webapps/novnc - No SSL/TLS support (no cert file) 2022-11-22 16:10:25,451 DEBG 'start' stderr output: - proxying from :6080 to localhost:5900 2022-11-22 16:10:27,274 DEBG 'start' stderr output: Can't open display 2022-11-22 16:10:29,279 DEBG 'start' stdout output: [info] tint2 not running 2022-11-22 16:10:29,291 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2022-11-22 16:10:29,292 DEBG 'start' stderr output: tint2: could not open display! 2022-11-22 16:10:39,299 DEBG 'start' stdout output: [info] tint2 not running 2022-11-22 16:10:39,311 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2022-11-22 16:10:39,312 DEBG 'start' stderr output: tint2: could not open display! 2022-11-22 16:10:49,319 DEBG 'start' stdout output: [info] tint2 not running 2022-11-22 16:10:49,330 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2022-11-22 16:10:49,331 DEBG 'start' stderr output: tint2: could not open display! But I got the error message on VNC site: document.getElementById(...) is null addTouchSpecificHandlers@http://192.168.0.8:6080/app/ui.js:222:18 start@http://192.168.0.8:6080/app/ui.js:78:12 prime/<@http://192.168.0.8:6080/app/ui.js:45:27 I already updated to 6.11.5

ok thank you, now I was able to found my problem. I had to add chmod u+x to the delete_key and fetch_key scripts within my go file. The /boot is a vfat formated stick so it doesn't understand these rights. So now its working

Hi, thanks for all the good information about this topic. Currently I try to use it with the "next" Unraid 6.9.0-rc2 release. Its not working for me, therefore I wanted to ask if anyone has already tried this. Maybe the problem is about the event folder: ls -la /usr/local/emhttp/webGui/event/ drwxr-xr-x 2 root root 60 Aug 31 2018 array_started/ drwxr-xr-x 2 root root 60 Mar 2 2019 disks_mounted/ drwxrwxrwx 2 root root 60 Jan 27 23:42 started/ drwxrwxrwx 2 root root 60 Jan 27 23:42 starting/ drwxrwxrwx 2 root root 60 Jan 27 23:42 stopped/ drwxr-xr-x 2 root root 60 Aug 31 2018 stopping_array/ drwxr-xr-x 2 root root 60 Mar 2 2019 unmounting_disks/ Are the folder / event names changed to the new names: array_started, disks_mounted, stopping_array and unmounting_disks? started, starting and stopped just containing the delete_key and fetch_key scripts I've copied to this location. Thanks in advance Namru

First steini84, thanks for you amazing work! I have just a short question. Do you have any information about a new zfsonlinux version > 0.8.3 which supports a kernel like the 5.5 because 0.8.3 supports only 2.6.32 - 5.4. I was not able to find a solution for this issue but I found error reports regarding 5.5 and 5.6 kernels. Additional I think there was some discussions about a functionality change that breaks some not fully GPL compliant modules. Thanks