ich777

Nothing to worry about. 😉

It's almost the same as for the Debian Bookworm container, please take a look here. BTW, this works also with Authelia.

It is also mentioned in the description.

Are you sure that the path in your case is correct. Please read this post from the second paragraph on:

Sicher das der Fehler nirgends anders liegt? Wenn du alle rausgenommen hast sollte dir der lancache eignetlich nicht mehr dazwischenfunken. Wenn du den DNS bei deinem standard DNS Server lässt läuft alles?

That grow over time and I never expected to have that many container/plugins. But better than on Discord, that's why I avoid Discord. Most of the times the questions that I get are something that could have been figured out if the description from the container or the variables in my templates would have been read... So to speak the basic documentation is there so that everyone can set up for example a game server. Also don't forget that we are community developers and are strictly speaking not related to Unraid.

Not possible, because each individual Unraid version needs all drivers to be recompiled and then uploaded so that users can download them, it's not like if you are installing a driver on Windows. You are basically downloading a precompiled Nvidia driver version for your specific Unraid version if you install a driver through the plugin and yes I have to store all the drivers for each individual Unraid version.

Just to clarify: When you are not updating and just rebooting the server while the driver version is set to a specific version on the plugin page it will stay on that driver version (even if it isn't anymore in the list <- this can happen when Nvidia releases much drivers in a short period of time). When you are updating the Unraid version and the static driver version that you've selected is not available for the new Unraid version it will go back to latest <- what should the plugin else use? These are two different things and only in one case it will go back to latest.

That's not what I've said... I really don't understand why you can't answer my questions but sometimes I really can't help it seems...

You are not alone. You still have not said what you've did. Did you just reboot? Did you up- or downgrade the Unraid version? Where are your Diagnostics? I would really like to see two sets of Diagnostics from you on after you set the driver version to a static version on the plugin page and then another one after a reboot of your server after it changed back to latest.

I think you missunderstood, if the specific driver version that you've selected is not available for the new Unraid version that you are up- or downgrading I have to fall back to the latest available version. It does because the second bullet point is only true if you are up- or downgrading the Unraid version. As said across reboots (without a Unraid up- or downgrade) I can't reproduce what you are experiencing and the version just stays the same as what I selected in the plugin. Or do you mean that I should keep all driver versions for all Unraid versions?

The above doesn't sounded like that and English is also not my native language. For a running Unraid version or if you upgrade to a new Unraid version? If we are talking about a running Unraid version nothing should happen. If you are upgrading or downgrading to another Unraid version where that specific driver version is not available it will indeed fall back to the latest option since this is the only viable option for me since the plugin can't know what version one would like use now.

I know what you've reported but it's no issue on my system and I can't reproduce that. Do you upgrade or downgrade you Unraid version? Which driver version are you using? Sorry but can you please calm down. I'm trying to help but you even didn't include Diagnostics from your system so that I can see what it did, you even didn't provide what happened (reboot, plugin update,...).

Please read this post:

Did you stop the server, then edit the config and then start the container again. If you simply restart the container the settings will be discarded. Sorry I can't help with that since I don't know that. Maybe ask in his support thread/GitHub.

Sorry, aber nur weil du es in einem YouTube Video siehst heißt es nicht das du es auch so machen sollst. BTW ich kann mir nicht vorstellen das er diese IP benutzt hat, zumindest nicht für den Server. Vergiss auch nicht auf YouTube ist auch nicht alles richtig, sogar mehr falsch als richtig.

Which file did you edit (location)? How do you try to connect? Here are examples: If you are running the container in br0 mode this won't work OOB if Host Access is not enabled in the Docker settings.

May I ask why do you run the container in br0? As I explained in that thread that you've found it has no real advantages...

I think you should have been looking at the start, fist post:

You could also achieve that with a custom bridge network, as said above, in my opinion that's a bit overkill and not necessary because you the port assignment is the important bit. However that's all up to you.

You could also enable Allow Host Access in the Docker settings to circumvent that. May I ask why did you even set it up as br0, in my opinion this makes no sense and has not really any benefit.

Even 32GB is too less RAM for Palworld. Yes, multiple people with less than 64GB of RAM reported that that they got OOM (Ot Of Memory) errors. You can limit the amount of RAM that the container can consume but if the container runs into that limit it will ultimately crash and restart (because I use --restart=unless-stopped for my container) but keep in mind that this can cause corruption from the savegame. My container currently consumes with three people on it about 20GB: ...but I've seen higher values, near to 30GB too (mine is currently limited to 50GB as you can see in the screenshot).

Please read this post:

No, this is from the developers themselves where the project lived on their system and how it was built.

I see nothing obvious in your Diagnostics sorry. But it seems that Palworld tries to access memory that it's not allowed to access but as said, that could be maybe also caused by bad RAM. I also have 128GB installed but don't have had any issues so far on my system but I have to say that I only have nine concurrent players on the dedicated server. Maybe someone in the official Discord can help here but if there also nobody knows my guess is bad RAM or something like that. New RAM can also be defective.