ich777

No, the server is running fine when I tested it the last time, sure this message is still there but it is running, that's why it's again available in the CA App. You just have to make sure that you've forwarded all ports before running the container because otherwise the dedicated server will restart after a bit if the ports aren't forwarded properly.

The default ones, I didn't change a single line in the default template. Please remove your Steam credentials! The Steam credentials are only needed if they are marked as required with the red asterisk and not hidden away under the Show more settings...! Please don't say that you entered Steam credentials for Palworld... Again, they are only needed if they are marked with the red asterisk and not hidden away. EDIT:

No issues over here: I just saw that you are using a 3rd Gen Intel Core CPU, it could be the case that this CPU is too old to run and missing instructions that the game can run properly but I'm not to sure about that.

Then this seems like a power related issue since otherwise you would get a Kernel panic. If the power cuts out and the server restarts or simply freezes then it is most likely the power supply can't quiet cover a peak. That is maybe caused by the GPU in combination with the CPU since these are pretty intensive workloads and both can be hit quiet heavily initially, cause a spike and the over current protection hits.

As @alturismo already pointed out, XID 79 is a pretty generic error but most of the times related to the card itself, you can get more information here.

It would be really beneficial to know what you've did and how you've set everything up? Do you have screenshots and snippets from your config? For example on my server I have a CS:Source server on port 27030 and a CS2 server on port 27029 Wreckfest is running on the default ports 27015 and 27016 (all ports listed are UDP).

Are you sure that your power supply is up to the task since most of the times it has to do with the power supply. Do you have a display connected to actually see what's going on? It would be really cool if you have a display connected and you could take a picture what's happening on screen when it actually crashes. I assume your machine is not automatically restarting? I see nothing obvious from your syslog, the driver loads fine and it should in theory be working.

That's strange, I try the container tomorrow and report back if it is working as expected on my machine.

No, the lower one, are you sure that everything is located on disk1? Have you changed anything else in the container template? On what hardware do you try to run the container?

You should really include your Diagnostics since no one knows how your Unraid server is configured in terms of network. This would be also be better suited in the Bug Reports subforums however, I think you are the first that reports such an issue. @JorgeB & @itimpi & @JonathanM did you hear about that before?

Aber das sagt doch nix aus, war denn eine Last am Controller sprich hast du was kopiert? Hast du das Bild durch das Glas gemacht? Hast du Airflow im case oder nicht, ich spreche hier von viel Airflow und nicht so nur ein wenig da die Karten richtig viel brauchen wie @DataCollector schon geschrieben hat. Ich würd dir empfehlen das du einen 40mm Lüfter drauf montierst. War es nicht auch so das er Abstürzt wenn du was auf die Disks schreibst? Welche Festplatten hast du eigentlich verbaut SATA oder SAS? Brauchst du denn überhaupt so einen Controller? Hab mir jetzt nur zwei Platten angesehen aber das sind doch SATA oder?

Please see the second recommended post on top of this thread.

You could install everything into a LXC container and use it there just as another idea.

Ein Intel Board... sieht man auch nicht alle Tage... Hast du mal nachgesehen ob ein BIOS update gibt für das Board selbst? Bitte versuch auch mal das Management Interface sprich den integrierten VGA Controller zu deaktivieren. Bist du dir auch sicher das deine LSI SAS3008 PCI-Express Fusion-MPT SAS-3 nicht überhietzen (weiß nicht welches case du verwendest und ob da genügen Airflow drüber läuft).

Please post your Diagnostics before doing all of that and also the file: /boot/config/plugins/nvidia-driver/settings.cfg I assume you are referring to Docker containers? Yes, the containers won't be able to start when the driver is removed after the first reboot, after the second restart you should be up and running again just fine. May I ask why did you click the Download button in the first place? Was something not working or did you simply just try to change the driver?

I know that issue but I haven't figured out why this is the case for Wreckfest since it seems that even if you change the ports and forward them correctly in the template that Wreckfest won't accept the change and somehow you won't be able to connect, to circumvent that I change the ports from other game servers to be able to run Wreckfest, I also have to say that they changed quite a lot since I've created the server and it is now maybe possible to change the ports. IIRC Wreckfest is one game that needs to be reachable from the outside world so that you can join even if you want to join a LAN game (but I'm not 100% sure anymore about that). If you want to I can try it when I got home from work because I have still installed the dedicated server but only start it if I play with some friends on it. EDIT: If you want that the game honors the server_config you have to enter that IIRC at GAME_PARAMS: -s server_config=server_config.cfg (but I haven't used a server_config.cfg in a long time and don't quiet remember exactly)

To what are the paths set in your template? Gmod is one server that needs the real file path to your game files so to speak /mnt/cache/... or /mnt/disk2/... and not the FUSE file path /mnt/cache/... If you however use /mnt/user/... it will segfault indefinitely.

Please remove the Nvidia Driver plugin, reboot, install it from the CA App and reboot or restart the Docker service. What did you do? Did you upgrade your Unraid version or did the plugin notify you about a new driver update?

There is no official release out there with Kernel 6.7.5, can't help with third party Kernels.

Wie schon oben geschrieben, das ist ein BIOS fehler, steht auch selbst oben in der Fehlermeldung selbst. Das kann beispielsweise durch eine neue funktion im Treiber ausgelöst werden aber selbst dann kannst du dem Treiber nicht die schuld geben weil es einfach ein Fehler im BIOS ist und dort was schief läuft, deshalb steht auch dort das es ein Fehler im BIOS ist. Das taucht von Zeit zu Zeit im Forum auf und ist meistens mit einem BIOS update gefixt. Ich würd in deinem Fall mal ASUS anschreiben.

Not sure about that since I tried a few enclosures and most had a generic GUID which was alwas the same.

Das ist ein Firmware Bug und da kann nur der Hersteller vom Motherboard helfen. Sorry...

I reeally can't tell if they are really the same since I've stopped using pfSense because for home usage in my opinion it is a bit too complicated (granted it is very similar to OPNsense). Why? I thought you would like to use it from outside your network to connect to machines inside and outside your LAN. Usually pfSense will do a hair pin NAT so to speak NAT reflection and redirect the traffic if you are connecting from inside your LAN to your local address in the Firewall so that the traffic actually doesn't go outside your network. IIRC you have to configure that in pfSense so that it is working properly. You should first troubleshoot if NAT reflection is working properly on your Firewall <- this is beneficial for other applications that you've forwarded to the Internet too since these applications then will be also be redirected on your Firewall and the traffic will actually never leave your home network if you are accessing the services through your LAN with your domain name.

Das sieht mir nach einem Firmware Bug aus. Kannst du mal prüfen ob es eine neue BIOS version gibt und diese evtl. updaten? Ich kann leider nicht viel machen bei diesen Meldungen, du musst das dem Hersteller von deinem Motherboard mitteilen oder wie gesagt ein Firmware update machen. Above 4G Decoding und Resizable BAR hast du an im BIOS?

You should report that in the Frigate thread and not here since I don't know anything about the image and it not strictly speaking tied to the Nvidia Driver plugin if you have issues... I even don't know what kind of workload that Frigate is putting on the cards and also what other variables are you using in the template. It would be also beneficial if you include Diagnostics since I really can't tell what's going on on your server nor do I know what driver are you using and so on.