ich777

This line says that the container autmomatically installs the "old" driver but only because selected I think (I have built in a routine that checks if the container can actually get all releases and fall back to the installed one if it has no access to the internet or even Github. Please try to select 'latest' in the Plugin, press 'Update' and then restart (you can actually check what version would be installed before rebooting if you do 'cat /boot/config/plugins/nvidia-driver/settings.cfg' in the terminal). A few users also had that problem on the first few pages, I hope you don't mind me saying if you can read through that, I think a reinstall of the Container solves the issue, one user even said clicking 'force update' would solve the problem but I don't think that this is enough... Please keep me updated... Thank you for the frequent updates. If this is the solution to this problem I'll be very thankfull! Are the warnings from the syslog gone or they still in there? I also got another user on the German subforums that has a similar problem with a Asrock Taichi X570, I'm not sure if it's related to Asrock or newer AMD systems in general.

You have to add the manually add the Variable otherwise it will not show up in the template, but it's enabled by default... You can check that if you open up the log and see if you got messages that say: UPDATE CHECK: ---Nothing to do, Valheim up-to-date--- If you get this messages everything is working and the container checks for updates. Some routers are not capable of NAT reflection and then you can't connect with your external IP from your local network. If you forwarded the ports correctly (all 3 ports UDP) in your router/firewall try to connect from externally to your server with your public IP.

Also nur mal kurz was High-Water ist: Ich kann mich ehrlich gesagt gar nicht mehr an den thread erinnern weil das dann später gefixt wurde und ich das Problem jetzt auch nicht mehr kenne. Ich würd auch auf jeden Fall den Minimalen freien Speicher angegeben, den würd ich immer Eingeben, meiner Meinung nach eine der wichtigsten Einstellungen, solltest mindestens so groß einstellen wie die größte Datei die du drauf kopieren willst. Handelt es sich beim Backup um eine einzelne Datei oder sind es mehrere kleine?

Eventually someone has it running with guacamole but I can't really help since I don't use it that way...

No, this is the basic log. You can set Debug log to 'true' but that will completely bloat your log (in the template click on 'Show more'). Yes, the log will not get longer, but this is a good indicator that everything is working. Please try the Steam Server Browser (View -> Server -> Favourites -> Add Server -> Enter your IP eg: 192.168.1.10:2457 -> Add server -> Refresh). If you try it from ingame it's really buggy... Keep in mind this game is in early alpha and such bugs are very likely to happen. Your server is definetely running and people can connect. EDIT: Please keep in mind, most questions here asked related to the game and not to the container itself, so this questions should be asked on the Valheim Discord/Forums/Steam Community Hub. Also please read the second recommended post on the top of the Thread.

Hast du ein AMD System?

Hast du das Nvidia-Driver Plugin drauf bzw. verwendest du ein AMD System?

What system exactly? Intel or AMD? I think this has something to do with the AMD Platform since I only got now a few reports that it doesn't work on AMD Systems. Have to analyze this further. It could possibly be that this is only a small setting in the BIOS or solved with a BIOS update... Can you try if you experience crashes again to try different BIOS versions for your board? Can you take a few pictures of the BIOS especially for the PCIe Bus and set it to me via PM (eventually you find something about BAR and a setting that says Above 4G Decoding)?

Delete the old Plugin, Upgrade to 6.9.0 (after this your Plex container isn't able to start because the Driver is missing), go to the CA App and install the Nvidia-Driver Plugin (for a detailed explanation go to the first post of this thread), reboot. Please read this post and follow back the linked posts: Please make sure that you are on the latest Motherboard BIOS, check if you got above 4G decoding enabled. If this all doesn't help try to boot with Legacy or CSM mode. Please post the Diagnostics here (Tools -> Diagnostics -> Download -> drag the file here in the textbox) if you don't get it to work.

Please be sure to put in a minimum password length of 5 characters otherwise it won't work. If that isn't the problem, check if you're affected by the world destroy bug, delete the whole '.config' folder that is in your valheim folder. Eventually try start over (backup the 'Backups' folder frist from your 'valheim' directory to your local computer), delete the container from the Docker page then delete 'valheim' directory in your appdata folder and pull a fresh copy off of the CA Àpp and start it with the default settings. Exactly, these are completely game related problems and have nothing to do with the container itself. Please post such questions on the Valheim Discord/Forums/Steam Community Hub. That is only a Warning and can be ignored and will not affect the functionality of the game. You are having the game set to Public '0' please set this to '1' and you will be able to reach the server from your local network and also from "outside" (don't know why this has everybody set to 0 when the default value is 1). Also with which port are you trying to connect? The default would be LOCALIP:PORT+1 = LOCALIP:2757 I personally don't use Valheim Plus but from what I know it is possible to enable Valheim Plus and play without any progress loss, but keep in mind you have to install Valheim Plus to all the clients too and the exact same mods that you've enabled on the server otherwise you won't be able to connect. Try to backup the 'Backups' folder from your 'valheim' directory to your local computer in case something goes wrong.

Actually that's a game that I want a server for... From what I've know the Dedicated Server for Linux hasn't released or am I wrong? The Windows version of the Dedicated Server doesn't run stable with WINE. If they release a Linux Dedicated Server feel free to contact me and I will create one.

This is a known problem with Valheim if more people playing on the server, there is a workaround out there but I don't know exactly where... Please leave the developers of Valheim a short message about that on their Discord/Forums/Steam Community Forums, I think they will fix this soon.

Not as far as I know... And well in @nicknick923's case his Dell T310 delivers too less power on the PCIe slot...

Please look on the first few pages, a few users had this problem to, a reinstall of the container did the trick I think. There is no X server installed in Unraid so you can't use nvidia-settings because this relies on X server. I'm sorting this out currently with limetech. For now I can send you a package that you simply replace on your USB Boot device and reboot. Please write me a short PM and I will send you the link and also how to do it.

Yes but that's not that what this plugin is for and it doesn't support the old driver. From what I've read the card has a maximum TDP of 19,5 Watt also it's strongly dependent on how the manufacturer implemented the start of the card in the BIOS of the card itself, some cards go even without a driver into idle. One way I think would be that you boot into GUI Mode, eventually this will help. Or you create a VM, pass through the card and install the driver there. Eventually @SpaceInvaderOne has some idea to solve your problem.

What do you want to do with the card? You can't use it for HW transcoding or similar The card is pretty old from what I've seen, released 2013 and also Fermi2.0 (GeForce 4xx Series) based you need to be at least on Keplar (GeForce 6xx Series). The libraries are not compatible with the old drivers and won't work for use in Docker Containers. Please read this post:

Yes you can run them from inside the container with this command: '${STEAMCMD_DIR}/steamcmd.sh +login anonymous +force_install_dir ${SERVER_DIR} +app_update ${GAME_ID} +quit' But keep in mind that you are having a hard time to update a running game and the update will fail. Btw have you read this, if we are talking about Valheim: For example here: Click The log and the configuration looks good and indicate a successfull startup. If your Router/Firewall doesn't support NAT Reflection then you can't connect from your local network with your PUBLICIP:2457, I would first try to connect to with your LOCALIP:2457 If you forwarded the ports correctly in your Router/Firewall 2456-2458 UDP (and only UDP) then you should be able to connect to the server from outside with PUBLICIP:2457 Was the server running before because I see you are using a old template, version of the Container, if it was running before eventually you are affected by the world destroy bug (I built in a backup function in the Container so that you can restore the world if needed - see the second recommended post in this thread on the top for more information).

Wenn du es schon deinstalliert hast und neu gestartet hast kann es nicht mehr am plugin liegen.

Du hast eine Quadro 400 (bitte nicht mit der P400 verwechseln, die sehen auch fast gleich aus) und die wird vom Treiber nicht unterstützt. Hier kannst du nachsehen welche Karten das unterstütz werden für die aktuelle Treiber version: Klick Du kannst diese Karte nicht mit Unraid benutzen, zumindest nicht für das Transcoding in Docker Containern. Hast du neu gestartet? Wird auch im Plugin und per Meldung angezeigt das du neu starten musst um den Treiber vollständig zu deinstallieren.

Can you connect to Github? This seems like a network related problem since even Plugin the fails to download, have you got PiHole running somewhere in your network, if so eventually try to disable it. @Squid do you know that message on a Plugin installation? Never saw that before.

With which IP are your friends connecting. Please be sure to give them your PUBLICIP:GAMPORT+1 also make sure that only forwarded the ports for UDP and not TCP or TCP & UDP. Eventually your ISP is blocking the ports and a port forwarding isn't possible. Have you got other services running that are reachable from "outside".

This message can be safely ignored. EDIT: I think I should be creating a real support thread for the iSCSI plugin...

You know that I also put a screenshot of the red box (Step 3) and the text is in there, actually when you read the fist post Step 5 tells you what to do next and where to go: Actually if you read Step 7 it tells you why you have to do this: EDIT: Please do the first post step by step even if you don't have the red box...

Please read the first post everything is in there, simply click on the logo from the Plugin. Also you have to reboot or disable and reenable the Docker deamon for the Plugin to work -> why is also in the first post. Yes because I think you haven't rebooted or restarted the Docker daemon and the Docker dissapears because it simply can't find the runtime (also if you look at the message if you click Apply in the Plex Docker template and don't click DONE you will see that the creation fails and error out because of the mentioned reason).

Put the command in the go file. If you force a transcode of a stream then the CPU should not be hit that hard (but it could be that you didn't notice it because the CPU is actually really old and only dual core I think), but keep in mind that if you CPU is not capable of a fromat it will fall back to CPU transcoding and you have no benefit. For example if the iGPU is used in a Ryzen 3200G for transcoding of a 4K file to 1080p the CPU hovers around 10-15% (that's for transcoding the audio, subtitle,...), if you try to transcode a file without the iGPU the CPU utilisation is about 80-90%. EDIT: I don't think your CPU is capable of transcoding HEVC and I even don't think it's capable of transcoding any or most of h264 profiles.