ich777

Okay, this should do the job just fine. I'm not entirely sure what is going on on your system since I'm using a Intel i5-10600, are you sure that you have a fast enough SSD where the game files are on?

Keep in mind the "solution" that you are asking for is not a solution, it's a workaround a pretty hacky one too and as said I would not like to risk the savegames from users from my container. You should really contact the developers. However, you still haven't said what hardware are you using.

Sorry but I can't reproduce this at all, the server is running now almost 6 hours. However it could be possible that there's a memory leak but I would strongly recommend that you report that to the developers. BTW 16GB for a server with game servers on it is really not much... Most game server consume about 1-2GB per connected player, for example ARK in the early days consumed the whole time about 8GB of RAM and on top for each player about 1-2GB of RAM. Sorry but I won't implement something like that into the container because that's really risky since you can cause corrupt save files and other funky behavior, again please report that to the developers. On what hardware do your run the server, it could be also possible that your CPU can't keep up and one leads to the other and you consume more RAM than usual. It would be possible but that's a really hacky workaround and not a solution to a problem which the developers should fix. I won't implement that because of the above reasons.

An what is the error? These messages tells you that the server is running fine. I answered almost every single question in terms for Palworld on the last five pages (starting at the very bottom of page 365). Please read these pages first if you have questions. Please also note that the server list is completely borked currently and the Epic servers can't keep up with 1.3 Million servers. Here are instructions on how to set up a non community server and how to direct connect:

No because how should I do that? This is something the develops have to fix… Also a bit more details on your specific container/setup would be nice. How many players are on your server, for how long is it running and so on. EDIT: There are currently six players on my server and it consumes about 11GB which seems fine to me for that player count, if it is empty it hovers around 2GB and 3GB.

I answered almost every single question in terms for Palworld on the last five pages (starting at the very bottom of page 365). Please read these pages first if you have questions. Just deploy the container and you are good to go. Please also note that the server list is completely borked currently and the Epic servers can't keep up with 1.3 Million servers. Anyways, here are instructions on how to set up a non community server and how to direct connect: I'm not sure if that's possible. Sorry, maybe someone else can answer this question.

Why do you even want to log in? You don't need credentials. The Steam credentials are only needed if they are not hidden away under the Show more... settings and marked with the red asterisk. Please start over, delete the template, delete the directory for palworld and then pull a fresh copy from the CA App without entering credentials.

This is good that you see the messages, this means that the server is up and running. I would recommend that you don't create a community server at the moment and connect via direct connect with your IP/Hostname and Port, how to do that is described here:

Soweit ich weiß schon, ich bin mir nicht 100% sicher, wenn du intern eine IPv4 hast sollte das funktionieren. Vielleicht kann hier jemand anders helfen, ich hab leider keine IPv6 vom Anbieter. @sonic6 @alturismo @giganode @fk_muck1

I think you missread what I've meant, it says this: GPU does not have the necessary power cables connected. Are you sure that you've plugged in the auxiliary power to the card since it needs auxiliary power connected (I think it's a 8pin PCIe power cable from the PSU)? Yes, as long as you've connected the auxiliary power:

An what is the exact issue? The errors/warnings that you see are normal and won't prevent the dedicated server from running correctly. If the container is not restarting everything looks okay. If you have trouble finding your server please see this post here: If you have any further issues, I have already answered almost any possible question on the last 5 pages (starting at the very end of page 365). As a side info:

Did you read the first and second post in this thread how to get it working in a Docker container? The card is recognized just fine. Can you spot why it's not working: Jan 20 12:18:36 R730XD kernel: NVRM: GPU 0000:82:00.0: GPU does not have the necessary power cables connected. Jan 20 12:18:36 R730XD kernel: NVRM: GPU 0000:82:00.0: RmInitAdapter failed! (0x24:0x1c:1436) Jan 20 12:18:36 R730XD kernel: NVRM: GPU 0000:82:00.0: rm_init_adapter failed, device minor number 1 I also noticed this: Jan 20 12:18:36 R730XD kernel: NVRM: Persistence mode is deprecated and will be removed in a future release. Please use nvidia-persistenced instead. Did you install the user script from SpaceinvaderOne? If yes please remove it and simply append this line to your go file: nvidia-persistenced

Thanks! Really much apprechiated!

Please don‘t forget to say that he also has to do that: This won‘t work because we are dealing with Docker. He has to use his SERVERIP:GAMEPORT

Answered multiple times already, see:

Sure, where are your Diagnostics for further troubleshooting?

This is the problematic setting: I would recommend that you change it to Array -> Cache and after that invoking the Mover but please be also aware that I would recommend that you first stop the entire Docker service since if the Mover detects files which are currently in use it won't move those files. By changing this setting to Array -> Cache and invoking the Mover it will move all files in the appdata share back to the Cache and will ensure that it will stay on the cache (which in my opinion is the way to use the cache). With that the Array will be able to sleep, if nothing else is reading or writing to the Array. Also keep in mind if you have VMs running that you maybe also stop the VM service before invoking the Mover so that it can also move these files to the Cache. After the Mover is finished you can start the Docker (and VM service) again and it should all work as it was before (after that you will be able to change the path to the game files in the Valheim template back to /mnt/cache/...). Hope that all makes sense to you.

As I've already explained... I think you didn't read the post that I've linked correct, in the second paragraph it's explained why... Sorry but that is completely not true even if you've disabled RCON (which it is by default and the template also states that) the port was forwarded (the wrong port forward would have fixed that too btw). However I've never seen such what you are described with the ports and is technically not possible by default. Glad to hear that.

This is a thing that you have to request from the creator of luckyBackup on Sourceforge since I use it in the container.

Yep, I even think that at the time of release there where no dinosaurs yet. 😅 Since the game uses Unreal Engine 5 you need something recent (at least something like Intel 6th Gen+ if I‘m not mistaken).

What hardware are you using? I assume you are using pretty old hardware since this is a indication that your CPU doesn‘t support all necessary instructions.

That will work but none of the screenshots show your share settings from appdata, go to the Shres and click on appdata. I would strongly recommend that you let the appdata share on the cache and not kove it to the Array so that the Array can go into spindown. Of course that depends if you want to do that but the appdata share should stay always on the cache and should not be moved to the Array.

If you had no issues before and now got issues then please remove the plugin.

Exactly that was what I meant what the error is, do you have a screenshot from the message that you get or something like that? Did you search for it in the Community Browser like I mentioned here: Please make sure that the UID and GID is set correctly. You maybe have to do a chmod on the directory that you use for Palword since it seems like the container itself can't change the permissions <- it does this to make sure that the permissions are correct. These warnings/errors are not trivial and they won't prevent the container from running properly.

Glad to hear. Can you post screenshots what you did exactly? How does the configuration file look like? EDIT: I've tested it now and this is the solution: Please add this to the GAME_PARAMS: port=8212 After further investigation you don't need to change the port in the config file, simply append or put that in the GAME_PARAMS variable and it will work (of course if you want to use port 8212). Please also don't forget to delete the existing port mapping in the template for the Game Port and create a new one like that: Hope that helps.