ich777

Can you try something like parsec to connect to your VM and see if this is working?

Yes I know, already saw that the build yesterday failed on my side. Will try to fix this today. Fixed and updated.

Are you connected with RDP?

Kannst du bitte ein Foto vom Fehler machen und hier posten?

Why? I would rather recommend to install the drivers in the Container. Have you installed to container runtime in the container? I have to investigate further but don't hold your breath on this because I will be not much around in the next two months. You have to start it like this to get error messages: lxc-start -F CONTAINERNAME (the parameter -F stands for Foreground) Also Ubuntu won't work because it relies heavily on systemd which is not available on Unraid and the workarounds that I've found so far are not the reliable or better speaking good...

This container uses TigerVNC but I really don't like to switch over to it because of the performance difference.

This was actually done by design... However you should be able to change this by clicking on the little Arrow at the left side, click on the gear icon and select at Scaling Mode "Remote Resizing": This will fill the entire browser window with DirSyncPro and should fix this...

Ich versuch das auf meinem server mal und melde mich dann wieder.

So it also doesn't work or does it? If it is working they using for sure something else than TurboVNC... Please note that I'm using TurboVNC for a reason, because it's fast... I really don't want to go back to x11vnc which is not that fast and efficient as TurboVNC.

Why are so many people on 6.10.2rc3? 6.10.2rc3 is older than 6.10.2... Can you post screenshots and maybe what you've tested? Do you mean you've tested with Unmanic? At time of writing Plex crashes Alder Lake systems when using the iGPU for transcoding.

Fix released. I would strongly recommend that you delete the container entirely, also delete the directory that got created in your appdata folder for RapidPhotoDownloader and pull a fresh copy from the CA App since I've also updated the baseimage to Debian Bullseye.

This is a old build btw... Keep in mind that 6.10.2 is newer than 6.10.2rc3

From the testing with @RoyalJackV (I hope you was the one that I tested this with) it's a hit and miss and seems that it sometimes doesn't display in the list. I think that's caused because the server list is huge and the same was the case in the beginning for Valheim too (same game engine)...

Will look into this, maybe the installation routine has changed again.

Auf dem screenshot vom Mittwoch läuft der Server aber und wartet auf verbindungen. Hast du hier den Docker neu gestartet oder was willst du mir mit dem Bild zeigen? Auf welcher Unraid version bist du denn? Welchen Prozessor hast du denn verbaut? Startet der Container dauernd von alleine neu?

Sorry for the late response, completely overlooked your post.. It's not that simple from what I understand, QNAP builds different chips for controlling the FAN and temperature readouts into their NAS systems, even if it's the same model series. Best would be to create a GitHub issue over here and we can talk about it there, simply mark me with @ich777 and I will be notified. Stonyx, the maintainer, over on GitHub is very helpful with this and answers really quickly. I also contacted @Trunkton because he actually owns a QNAP NAS.

Exactly, I think I got that request about a year ago IIRC. If they implement it in TurboVNC let me know and I will update it in all my containers. Sadly it's an odd issue but I can't do anything about it.

Thank you for the report, this was simply a typo in the description, already corrected that in the template. Fixed, please change it back to LATEST and try to restart the container once more, it should now pick up the latest version just fine.

Yes. You have to be at least on 6.10.0 and even better would be if you upgrade to the latest 6.10.2 because then the terminal button is also working.

Yes, every stable release is supported. Try to upgrade to 6.10.2

Sorry but I have to say that something must be wrong on your side: No issue here whatsoever over ssh... (please ignore the one su attempt, had to change the password since I forgot it now that I changed it that many times... )

As said above this would be something for the Docker Engine sub forums since this is not strictly speaking an issue from the container, something with Docker itself went wrong, maybe the image wasn't mounted correctly anymore or something like that.

This is working in the VNC LXC container too:

Is your keyboard layout maybe wrong? Sorry I really don't know what could be wrong on your machine... It seems like that you mistyped the password or something like that... I can't imagine something else also it is working for everyone else from what I know... Also what is this line with: #Password: Unraid That's why I don't recommend connecting to the root shell, switching to a user shell and then try to switch to a root shell again. I also don't see why this makes any sense...

Try the following: Destroy the container Create a new VNC container with the name: DebianVNCTest Wait for the installation to finish Open up the browser and go to the noVNC webinterface from the container LXCContainerIP:8080/vnc.html?autoconnect=true In the taskbar click on the terminal Type in "su" and enter "Unraid" as the password Type in "passwd" enter "Unraid" and after that twice "12345" Type in "exit" Type in "su" again and "12345" When in the su shell type in "passwd debian" and twice "12345" After that you can change the shell with "su debian" but I would recommend to type in "exit" to go back to the debian shell (I never recommend to jump around the shells from a shell in a new shell and so on...) After beeing in the debian shell type in "passwd" enter "12345" once and after that type in "Unraid" twice (all commands without double quotes) You should end up with a passwords for the user debian "Unraid" and root "12345" No, just destroy the container and create a new one, maybe try picking a different name and that should do it (even the same name is fine...). Please don't do this!!! This will most definitely destroy mess up all your LXC containers!