2 minutes ago, syko91 said:

okay i need help with rust, so endgame wipe is wrong 

Timezone: GMT (ID=Europe/London, IANA=Europe/London)

the server thinks im GMT but im in indiana how do i change this

no matter what i add to rust it changes back to GMT after reboot do i add somthing to the docker

ive added -e TZ=America/Indiana/Indianapolis Extra Parameters: it still shows GMT 

 

12 minutes ago, syko91 said:

ive added -e TZ=America/Indiana/Indianapolis Extra Parameters: it still shows GMT 

Thats not a docker thing, thats a Rust thing. Rust states that you need to tell the rust server itself to overwrite the time zone. "wipetimer.wipeTimezone America/Indiana/Indianapolis" for example

49 minutes ago, Mainfrezzer said:

 

Thats not a docker thing, thats a Rust thing. Rust states that you need to tell the rust server itself to overwrite the time zone. "wipetimer.wipeTimezone America/Indiana/Indianapolis" for example

thank you

Sorry i forgot that info its the ark survival evolved docker and I haven't tried the local ip

1 minute ago, Hippoboy9 said:

Sorry i forgot that info its the ark survival evolved docker and I haven't tried the local ip

What about my other questions?

I dont know how much ram and CPU its getting Sorry about the limited information this is my 1st time setting anything up in docker

Edited October 17, 20242 yr by Hippoboy9

10 minutes ago, Hippoboy9 said:

I dont know how much ram and CPU its getting Sorry about the limited information this is my 1st time setting anything up in docker

Go to the Docker page, click on Basic View in the top right corner (to enable Advanced View) and look how much CPU and RAM that the container utilizes when the container is running.

Its using about 6 GB of ram and .10-.15% of the cpu

1 minute ago, Hippoboy9 said:

Its using about 6 GB of ram and .10-.15% of the cpu

Then it is most likely that the container is running and waiting for connections.

I cant find the server within the list

Just now, Hippoboy9 said:

I cant find the server within the list

Have you done a port forwarding?

 

Sorry but it is really hard to troubleshoot with almost no information...

Did you change something in the template?

Did you change something in a config file?

Did you already do a port forwarding in your Router/Firewall?

Do you have a static public facing IPv4?

Are you sure you are not behind a CG-NAT?

Are you sure that your ISP does allow incoming connections?

I'm hoping someone can help with an issue my Satisfactory server is having on unraid. Was working perfectly, but this very last update has made it stop working. 

This is an excert from the log:

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '*******' already up to date.
---Prepare Server---
---Server ready---
---Start Server---
--ERROR: Couldn't find a game executable, something went probably wrong with the download!---

 

(I've put the stars in for my game number!!)

The game runs fine as a standalone on my pc, but the server will not come online. The game sees it, but says offline. I have stopped and started the server docker container (as per the instructions!) but still doesn't work.

Any ideas anyone??

I have tried to remove and then reinstall the container, but still the same error!

Edited October 17, 20242 yr by DavidSCuthbert

Having some issues getting the DayZ server to pick up the new Frostline expansion/Sakhal map. Seems the new map can't be downloaded if you are using anonymous steam/don't own the content, and if you try with auth there's no way to provide your steamguard 2FA. Have tried grabbing the mpmissions direct from Bohemia github but still get an error 'cannot load world'. Will keep at it and report back if I have success. But wanted to post to suggest the DayZ community app is updated both to handle the new expansion that came out this week and to incorporate the fact that since February linux can now run the stable release as well as the experimental client. ✌️

13 hours ago, DavidSCuthbert said:

(I've put the stars in for my game number!!)

Why? This is just the app id from Satisfactory.

 

13 hours ago, DavidSCuthbert said:

I have tried to remove and then reinstall the container, but still the same error!

Can you please share a bit more information about your installation please, to what is the Game Files path in the template set, if it's set to /mnt/cache/apppdata/... you have to make sure that you appdata share is set to stay on the Cache so to speak the primary storage is set to Cache and the Mover takes no action.

 

It is most likely the case your appdata share is set to be moved to the Array/another Cache and that's what's causing the issue.

 

However you can also set the path for the Game Fiels to /mnt/user/appdata/... but I wouldn't recommend that since appdata should always stay on the Cache so that applications have quick access to the data.

11 hours ago, BionicHeehaw said:

But wanted to post to suggest the DayZ community app is updated

Can you please explain this a bit more in detail, does the container need to be updated?

I assume it is working as expected currently correct?

Hey, just FYI the openrct2 docker is not starting due to glibc errors. I was able to fix the issue by upgrading your Debian base image to trixie-slim instead of bookworm-slim, although you may want to take a more nuanced approach. 

2 hours ago, Jamxx said:

Hey, just FYI the openrct2 docker is not starting due to glibc errors. I was able to fix the issue by upgrading your Debian base image to trixie-slim instead of bookworm-slim, although you may want to take a more nuanced approach. 

Thank you for the report, I‘ll look into that.

Hello! I'm having an issue with the Conan Exiles container and I'm not sure what to do.

I spun up the container a couple days ago and got it online and working flawlessly. Friends and I played online with no issues until last night when I was told the server had gone down. When I looked at the logs for the container in Unraid, I saw the container going through what I think is it's start-up script only to close out the log's window and force me to reopen the logs every few seconds. I have finally managed to copy what it reports before closing the window.

 

I have had a similar boot issue with 7DTD and Satisfactory before but stopping the containers, removing the existing SteamCMD folder, and allowing it to reinstall that seemed to fix those issues, but this method has not worked to fix it. (7DTD still has an issue but I'm not sure if it's a game issue or a container issue.)

 

I'm not at all familiar with script writing or the actual making of containers so I don't know where or how to fix the PID invalid issue.

I'm not sure what would cause this issue to spring up either because the server was up and running perfectly fine less than 24 hours ago and has not shut down or altered from the original container settings aside from the path that SteamCMD and the server saves their respective files.

 

Any help would be appreciated as my friends and I have been enjoying playing on these servers and I've been enjoying being able to host these on my own hardware.

---Ensuring UID: 99 matches user---

---Ensuring GID: 100 matches user---

---Setting umask to 000---

---Checking for optional scripts---

---No optional script found, continuing---

---Taking ownership of data...---

---Starting...---

---Update SteamCMD---

Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'

Logging directory: '/serverdata/Steam/logs'

[  0%] Checking for available updates...

[----] Verifying installation...

UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1728594755

-- type 'quit' to exit --

Loading Steam API...IPC function call IClientUtils::GetConnectedUniverse took too long: 48 msec

OK

Connecting anonymously to Steam Public...OK

Waiting for client config...OK

Waiting for user info...OK

---Update Server---

---Validating installation---

Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'

Logging directory: '/serverdata/Steam/logs'

[  0%] Checking for available updates...

[----] Verifying installation...

UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1728594755

-- type 'quit' to exit --

Loading Steam API...OK

"@sSteamCmdForcePlatformType" = "windows"

Connecting anonymously to Steam Public...OK

Waiting for client config...OK

Waiting for user info...OK

 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)

 Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)

 Update state (0x5) verifying install, progress: 11.66 (531496563 / 4557615836)

 Update state (0x5) verifying install, progress: 37.68 (1717242594 / 4557615836)

 Update state (0x5) verifying install, progress: 58.85 (2682103370 / 4557615836)

 Update state (0x5) verifying install, progress: 80.14 (3652379955 / 4557615836)

Success! App '443030' fully installed.

---Prepare Server---

---Looking for config files---

---'Engine.ini' found---

---'ServerSettings.ini' found---

---Checking if WINE workdirectory is present---

---WINE workdirectory found---

---Checking if WINE is properly installed---

---WINE properly set up---

---Checking for old display lock files---

---Server ready---

---Start Server---

tail: invalid PID: ‘’

Terminated

 

Please check to what path are the Game Files in the Docker template are set.

 

If they are set to /mnt/cache/appdata/... (real file path) you have to make sure that the appdata share stays on the Cache and is not moved to the Array, to do that: Go to the Share settings, click on the appdata share, make sure the Primary storage is set to Cache, no Secondary storage is selected and make sure that the Mover takes no action.

 

You can of course set the path also to /mnt/user/appdata/... but do keep in mind that some dedicated servers have issues with this path (FUSE file path), like for example dedicated servers which are based on the Source engine and they simply will segfault and restart over and over again.

I don't recommend to use the FUSE file path (/mnt/user/appdata/...) since in my opinion the data should stay on the quick storage media that the Cache is usually on and it will also reduce overhead from the FUSE driver and CPU to use the real file path (/mnt/cache/appdata/...).

 

Reason behind all of this is that if the path is set to /mnt/cache/appdata/... and the appdata share is set to be moved over to the Array by the Mover is that the container can't find all of the data in /mnt/cache/appdata/... because some data is now also somewhere on the Array and this could also mean that maybe your save game isn't found after a container restart and various other funky behaviour.

Please read through the post above this one first and then go on here.

 

5 hours ago, TheOnlyJoumae said:

I have had a similar boot issue with 7DTD and Satisfactory before but stopping the containers, removing the existing SteamCMD folder, and allowing it to reinstall that seemed to fix those issues, but this method has not worked to fix it. (7DTD still has an issue but I'm not sure if it's a game issue or a container issue.)

I've never heard of anything like that to fix containers not starting or being in a reboot loop.

On 10/22/2024 at 5:46 AM, Jamxx said:

FYI

This is now fixed, please update the container itself by clicking force update on the Docker page (with Advanced View enabled in the top right corner, don't forget to disable it again).

On 6/4/2024 at 10:42 PM, ich777 said:

I now looked a bit more into that and it seems that it's related to how I pull the updates for this specific game because I have to pull it from GitHub and not actually SteamCMD.

I will look into that.

 

However for the time being please only delete everything except for the save game directory.

Not to beat a dead horse but I was just curious if anything ever became of this issue with the Longvinter Server Docker needing it's updates pulled from GitHub instead of SteamCMD.

Just deleted the docker again and reinstalled so that it would update and it reminded me of this thread.

2 hours ago, ANJ_ said:

Just deleted the docker again and reinstalled so that it would update and it reminded me of this thread.

Thanks for the heads up, I completely forgot about that...

 

Please update the container itself and will migrate over to use SteamCMD instead of their GitHub repository.

Also please note that the first start after updating the container will take a bit longer since the container will have to do a few things for the migration:

1. Backup the save game
2. Download the new files for the dedicated server from Steam
3. Restore the save game

(Please don't interrupt this process!)

 

After that you should be able to use the container as usual but now with SteamCMD.

Hello, I finally got working the assetto corsa docker via ac manager, I got it to show up on the content manager,(Ports are forwarded) now I try to join via lan but I get a infinite loading screen with at the bottom says connecting, following with my ip:port number. Is there a way to know what's causing this and why I can't join?

34 minutes ago, sean1325 said:

Hello, I finally got working the assetto corsa docker via ac manager, I got it to show up on the content manager,(Ports are forwarded) now I try to join via lan but I get a infinite loading screen with at the bottom says connecting, following with my ip:port number. Is there a way to know what's causing this and why I can't join?

The server doesn't restart after a few minutes? If it does restart then this is a good indication that something is wrong with the port forwarding or the Master Server form AC cant connect to your Server.

 

Do you find your server on the server list? Usually it should show up there.

 

Can other people join your server from outside your local network?

If yes then it's most likely the case that your Hair Pin NAT (also NAT reflection) is not working properly.