ich777

How did you do that exactly? It would be way better to create a share that is located on the cache or a single disk and use it in that way like mentioned /mnt/cache/lxc or /mnt/diskX/lxc or whatever. It can also be the case that this is caused because you are created the share at /mnt/ Have you created this RAM disk by hand and mounted it to /mnt/lxc?

But how did you do that? All user shares are created within /mnt/user/ or better speaking /mnt/DISKNAME/ So if you selected the path /mnt/lxc it got ultimately created in RAM…

But this share doesn't exist or am I wrong, or how do you created that share, is this running off of a ZFS share? It was meant that way that you select a path to a physical share (like /mnt/disk1/lxc or /mnt/cache/lxc) and not the FUSE file path like /mnt/user/lxc

Have you got the Diagnostics when that happened? What path for LXC have you chosen?

Driver should now show up in the plugin, if not wait about 6 minutes and see if it shows up after that.

Tesla cards are not supported by this plugin, only consumer cards.

ATTENTION: This container is now deprecated because the official container now also fully supports AMD/Intel/Nvidia hardware transcoding. This container is fully compatible with the official Jellyfin container, to switch over to the official one simply change the repository in your Docker template from 'ich777/jellyfin' to 'jellyfin/jellyfin' like: From: To: and click in the Docker template, this will pull the official image. If you got any questions feel free to create a post! Thank you for all the support and feedback for this container!

You can join @Spectral Force's Discord, maybe someone can help you out there: Click He helps me with 7DtD support since I don't play the game. BepInEx is basically a mod loader which enables you to add mods to your server and it maybe has to be also installed on the client (your Computer) so that clients can join, but that always depends on the mod that you are installing and if it's a server/client mod or if it's a client mod only.

This shouldn't be an issue at all, even on my server it's the same: The issue with this is a bit more complicated and should not cause any issues whatsoever. It should be resolved after a few hours or days, this is not really an error message, this is more a warning.

This list is only used so that the plugin can determine which are the latest versions from the driver so that it can display the latest versions correctly. Exactly, because my toolchain only compiles the latest production, new feature branch, legacy 470.x.x driver and if a beta driver is available. Each driver has to be compiled for the individual Unraid version… Can you name a specific version so that I can trigger the build?

Have you yet seen this: Click I have not released this to the public because I have no testers out there and this it is in "beta"... You can install it by simply putting this line into the plugin installation: https://raw.githubusercontent.com/ich777/unraid-prometheus_smartctl_exporter/master/prometheus_smartctl_exporter.plg

This should be fine, since the SHUTDOWN temperature is set to ~105 °C I think... The shutdown is only triggered to my knowledge when the shutdown temperature is reached and it is recommended to reboot after it was triggered, not to reset the device. Anyways, keep me updated... BTW You can of course set the Shutdown temperature to something insanely high but keep in mind that these Coral devices can be a fire hazard (even the official documentation mentions this) when used wrong. Keep in mind I won't recommend to do this because if it really runs sometimes too hot it can simply catch on fire.

Have you yet tried the User Script that I've linked multiple times in the GitHub Issue that you've linked?

No, see the first recommended post on top of this thread for example. No, but why would you do that? If you want the server to be reachable from outside you have to change the ports anyways if they are already used by another game server because otherwise this could lead to issues if you want to make it available from outside (WAN).

I've noticed that sentence above, what games do you want to run on it? Please keep in mind that if you are exceeding the pre allocated VRAM that your entire VM manager can crash and this will most likely cause if you try to reboot your server in a hard reset, just to keep that in mind. I recommend GVT-g only if you know what you are doing and for light Office work or casual browsing. There is nothing I can do about that because most motherboard manufacturers also haven't implemented the VRAM allocation in the BIOS properly (see second recommended post on top of this thread).

Yes, the plugin will blacklist the module for you automatically if you don't have it already blacklisted on installation and after a reboot everything should be fine, didn't notice that you don't rebooted already... i440fx is basically a pretty "old" emulated machine type where Q35 is the modern one, AFAIK GVT-g won't work on i440fx machines, keep in mind changing from i440fx to Q35 may also involve reactivating Windows because you are basically changing the "motherboard".

If you have both installed (even if you have Intel GPU TOP alone installed) you can blacklist the iGPU and the plugin handles the activation. So no difference there…

Since you‘ve posted no diagnostics I can‘t tell on what Unraid version are you but I think that you are on anything greater than 6.9.0 If you are on 6.10.x you have to do that because the module would be loaded early in the boot process and I have no chance of reloading it with the GVT-g parameters so that everything will be working correctly. You will notice no change at all except for that that GVT-g will work afterwords. Have you also installed the Intel GPU TOP plugin? Diagnostics would help a lot…

Can you share the full log please? It can also be the case that the container image became corrupt, please try the following: Delete the container (don't delete the folder in your appdata directory for Thunderbird) Go to your Docker page and click "Add Container" at the bottom From the drop down select your Thunderbird template (this makes sure that it is the same configuration as before) Click on Apply to install the container again Please report back if that solved the issue. If not, share the full log and also a full screenshot from your Docker template.

Have you yet tried to set up a Valheim server on Unraid just to check if that works? I think this can be only a configuration issue since it's working for all other users including me. Try the following: Delete the container Delete the folder for ProjectZomboid which is located in your appdata directory Pull a fresh copy from the CA App and leave everything at default Make also sure that you've point the IP in your router to your Unraid server and the ports which are configured in the template (don't change them in the template). As said above, it works just fine in the default configuration.

Hair Pin NAT is that your router translates your Public IP from your LAN to the Internal IP and reroutes it so that the traffic doesn‘t goes over the Internet. How did you check that the ports are closed? Please note that most game servers won‘t display that the ports are open on sites like portchecker or something like that because they use another protocol and they don‘t answer to port check requests. bridge No, just opened the ports in my firewall and entered the LAN IP form my server. Please keep in mind that some ISPs maybe block traffic on some ports or even UDP entirely, I would try to contact your ISP if they block any traffic by default that is out of your control.

Yes, a user on GitHub requested that I should switch over to the 64bit version from ArmA3 by default, but that gives me so much trouble in the last time that I'm not sure if I should switch back over to the 32bit version. You can do this manually by adding this to the container template: Please report back if it fixes the issue.

Sag mal was machst du auf deinem Server? Ernsthaft... was hast du umgestellt, du hast vom mover das logging an geschaltet, frag mich nicht wo man das machen kannst aber du hast es auf jeden Fall geschafft... Willst du Überblick haben was der Server macht oder warum hast du das an geschaltet? Ich würde dir empfehlen nicht alles zu loggen, das interessiert doch auch keinen... ^^ Kontrolle ist schon gut aber wenn man es übertreibt dann kommt eben sowas raus...

Oh, completely forgot to wrote back, I've tried this on my server and I have no issue to connect to the server even from a computer outside my LAN. Can it be that this is a hair pin NAT issue in your case? So that people can connect from outside but people on your LAN have to use your LAN IP instead of your Public IP? Some routers doesn't support this properly.