ich777

Please go into the Docker template and see this: On the Docker page click on the container icon and select "Logs" copy everything in that window, put it in a text file, save the text file and drag the text file here into the text field.

Can you please provide a screenshot from the Docker template from this container? Which Krusader container are you using (repository)? Have you yet tried another Krusader container from another maintainer? BTW Thanks for the detailed explanation, this might be really useful in the future.

Can you describe what you've did exactly when reinstalling the container? I will try this today evening. Have you yet tried to force validation? Can you please provide a log?

@rezo I've now tried it and I can see the block device on the Initiator side: I'm also on rc18 to compare apples to apples (also the Initiator side): And this is on the Target side: There must have changes something on the QNAP side, maybe try to recreate the Target and also everything on the Initiator side.

Sorry I forget to attach the log: satisfactory.log This is from a fresh installed container.

Sorry but I cannot reproduce this on my end. On what Unraid version are you? Does it not work since the update correct? Can you try to set up a second instance on your server and see if it's the same? Have you yet tried to force a update by setting validation to true (please don't forget to disable it again after it pulled the update)?

It seems that the connection is established successfully. I will try that ASAP on my system. Did maybe change anything on the QNAP site? Have you yet tried to connect from another machine to the Target?

I will set up a Satisfactory server tomorrow on my server and I will report back.

What happens when you select your target and click reconnect?

Have you yet tried to set up a second instance and see if the second instances is working as described above?

What did you do exactly? Did you upgrade to a newer Unraid version? Do no devices appear in Unraid itself?

Please try to use the version from @binhex which has a VPN built in and see if it's the same.

Do you get /dev/dvb with the LibreELEC package? I don't think that's a driver issue because the plugin page actually lists your tunes (this is pulled from the /dev/dvb directory itself. Did you check the directory on the host or in the container? Any logs you can provide? Please install the LibreELEC drivers, reboot and post your Diagnostics.

If you are using Plex, you have to use a "bridge" since DigitalDevices are not supported, please look at the recommended post on top.

Have you yet tried the DigitalDevices driver package? I see that you are using the LibreELEC package. Which version is your DuoFlex tuner? The user from the post that you've linked has had a really old version from the card IIRC. What is your exact issue?

Please remove the sound driver plugin, reboot and see if that makes a difference. It is nice to see that you are using this plugin but I'm currently not supporting it officially since I have not enough free spare time to do so. I think it might be the cause of the issue. If it's the cause of the issue I will maybe fix this for the next Unraid version.

Please post your Diagnostics.

I created an Issue on GitHub over here, I hope that's okay for you and that I included a few files from the Diagnostics. I always recommend to use the official image for testing purposes if you experience such issues.

This is not what I've wrote, you have to use all CAPS at the Key: FIREWALL Try to remove this if the FIREWALL variable won't fix your issue.

I see this from time to time but I really can't tell why this is happening, I can't reproduce this over here. As you've already discovered a reinstall most of the times fixes this (of course back up your saves in the first place).

No worries about that, I write a physical file which keeps track of the version because there is no easy way to keep track else.

Sorry but I'm really not familiar with these tools because I don't use torrent... How does this even work? Are you sure the Maybe they are right but I really can't tell what's going on there. It shouldn't leak the IP, you can however try to enable the Firewall in the OpenVPN-Client this will prevent communication if no VPN connection is established. To do that simply create a Variable with the Key: FIREWALL <- this is enough, you don't need to enter a value. Can you please also send a picture from the Extra Parameters from the OpenVPN-Client container?

No, however you can stop the container, download the alpha version, extract the contents into the server directory by overwriting the old files and then start the container again, please note that you should back up your configuration for ValheimPlus first before doing that.

Frag doch mal @i-B4se der hat eine Dual Edge TPU, der kann dir sicher mehr infos dazu geben, ich hab meine Dual Edge TPU grad nicht eingebaut und die liegt nur im Keller rum.

This is not an error and if you would have looked more often in your logs you would have noticed that this message is in the log for about two months and has updated the container I think about two times (with that message in the log). I have now tried it and I can connect fine to the new version. Are you sure that it doesn't show up in the steam server browser? How much resources does the container use? If it looks like this it is running and waiting for connections: Here is also a screenshot: