Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] ich777 - Gameserver Dockers

Featured Replies

On 3/4/2022 at 9:30 PM, ich777 said:

Have you installed a cache drive?

When does it wipe the map exactly? When you connect to the world?

Have you installed any mods?

so sorry for the late reply!!

1. cache drive?

2. It wipes usually in the early morning, it crashes, boots everyone out, and on restart its wiped
3. no mods

  • Replies 12.5k
  • Views 2.2m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Just thought I'd share my experience setting up a Valheim server with this docker app from @ich777(thank you!)   You don't need to worry about Steam authentication for Valheim, the default a

  • Dockers Available:   SteamCMD DedicatedServers: CounterStrike: Source CounterStrike 2 TeamFortress 2 ArmA3 - requested by @MrSage Deathmatch Classic

  • This will hopefully shed some light on the underside working bits of building a cluster of servers for ARK:SurvivalEvolved.   With the inspiration (read thievery) from @growlith I present th

Posted Images

  • Author
6 hours ago, turnipisum said:

Looks like it just cycles through the steamapi bit and fails

Can you try to create a variable like in this thread:

 

  • Author
6 hours ago, deamonsatwar said:

1. cache drive?

Yes, a cache drive for Unraid? If yes, to what is the cache drive set in terms of Use Cache in the Share settings?

 

Can you share a screenshot from your entire Docker template?

is there something wrong with the Valheim docker files? Unraid cant download those anymore?

  • Author
1 hour ago, domrockt said:

is there something wrong with the Valheim docker files? Unraid cant download those anymore?

Can you be a bit more specific please?

I've now tried it and it works flawlessly, here is the output from the Docker pull command:
 

Pulling image: ich777/steamcmd:valheim

IMAGE ID [valheim]: Pulling from ich777/steamcmd.
IMAGE ID [a2abf6c4d29d]: Already exists.
IMAGE ID [2093c0a488bc]: Already exists.
IMAGE ID [9164366befb9]: Pulling fs layer. Downloading 100% of 11 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [273c8055b36c]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [753e1ebc1953]: Pulling fs layer. Downloading 100% of 3 KB. Download complete. Extracting. Pull complete.
IMAGE ID [75859e523978]: Pulling fs layer. Downloading 100% of 3 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
Status: Downloaded newer image for ich777/steamcmd:valheim

TOTAL DATA PULLED: 11 MB

 

And here is the container log: valheim.log

 

Everything is working as expected, at least on my server.

when i redownload Valheim it does not load any Files,  i disabled the check but still no game download.

 

 

1151479516_Screenshot2022-03-07164359.thumb.png.c7861dae5c4e951320547326c54659bf.png

1 hour ago, ich777 said:

Can you be a bit more specific please?

I've now tried it and it works flawlessly, here is the output from the Docker pull command:
 

Pulling image: ich777/steamcmd:valheim

IMAGE ID [valheim]: Pulling from ich777/steamcmd.
IMAGE ID [a2abf6c4d29d]: Already exists.
IMAGE ID [2093c0a488bc]: Already exists.
IMAGE ID [9164366befb9]: Pulling fs layer. Downloading 100% of 11 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [273c8055b36c]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [753e1ebc1953]: Pulling fs layer. Downloading 100% of 3 KB. Download complete. Extracting. Pull complete.
IMAGE ID [75859e523978]: Pulling fs layer. Downloading 100% of 3 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
Status: Downloaded newer image for ich777/steamcmd:valheim

TOTAL DATA PULLED: 11 MB

 

And here is the container log: valheim.log

 

Everything is working as expected, at least on my server.

 

do you believe in the possiblity that the User is mostly in fault? 

i borked up my cmd files... It works again :D my bad sry for interrupting!! 

  • Author
29 minutes ago, domrockt said:

do you believe in the possiblity that the User is mostly in fault? 

i borked up my cmd files... It works again :D my bad sry for interrupting!! 

So everything is working again for you?

What CMD files are you talking about?

 

Do you changed anything within steamcmd.sh?

18 hours ago, ich777 said:

Yes, a cache drive for Unraid? If yes, to what is the cache drive set in terms of Use Cache in the Share settings?

 

Can you share a screenshot from your entire Docker template?

image.thumb.png.01596a864dc2996a0f51608e17a51b9e.pngim actually not entirly sure about the cache drive my husband set up unraid ill have to ask him. for now heres the screenshot you asked for

  • Author
5 hours ago, deamonsatwar said:

im actually not entirly sure about the cache drive my husband set up unraid ill have to ask him.

Looks like you have no Cache disk installed.

Can you change the "ServerFiles" path to: /mnt/user/appdata/valheim instead of /mnt/disk1/appdata/valheim?

 

Maybe this will help in your case.

Hii all,

 

Have been running Valheim server for 5 month without problem but that is one thing that bothers me. When i check Unraid log i get this in the log and have checked it is from Valheim docker. Is any way to stop this?

 

 

Mar 9 18:09:36 Tower avahi-daemon[8233]: New relevant interface veth96d3b5b.IPv6 for mDNS.
Mar 9 18:09:36 Tower avahi-daemon[8233]: Registering new address record for fe80::c8eb:95ff:fee4:ab27 on veth96d3b5b.*.
Mar 9 18:09:59 Tower kernel: vethf96353e: renamed from eth0
Mar 9 18:09:59 Tower kernel: docker0: port 1(veth96d3b5b) entered disabled state
Mar 9 18:10:02 Tower avahi-daemon[8233]: Interface veth96d3b5b.IPv6 no longer relevant for mDNS.
Mar 9 18:10:02 Tower avahi-daemon[8233]: Leaving mDNS multicast group on interface veth96d3b5b.IPv6 with address fe80::c8eb:95ff:fee4:ab27.
Mar 9 18:10:02 Tower kernel: docker0: port 1(veth96d3b5b) entered disabled state
Mar 9 18:10:02 Tower kernel: device veth96d3b5b left promiscuous mode
Mar 9 18:10:02 Tower kernel: docker0: port 1(veth96d3b5b) entered disabled state
Mar 9 18:10:02 Tower avahi-daemon[8233]: Withdrawing address record for fe80::c8eb:95ff:fee4:ab27 on veth96d3b5b.
Mar 9 18:10:05 Tower kernel: docker0: port 1(veth619de24) entered blocking state
Mar 9 18:10:05 Tower kernel: docker0: port 1(veth619de24) entered disabled state
Mar 9 18:10:05 Tower kernel: device veth619de24 entered promiscuous mode
Mar 9 18:10:05 Tower kernel: docker0: port 1(veth619de24) entered blocking state
Mar 9 18:10:05 Tower kernel: docker0: port 1(veth619de24) entered forwarding state
Mar 9 18:10:05 Tower kernel: docker0: port 1(veth619de24) entered disabled state
Mar 9 18:10:10 Tower kernel: eth0: renamed from veth88d9518
Mar 9 18:10:10 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth619de24: link becomes ready
Mar 9 18:10:10 Tower kernel: docker0: port 1(veth619de24) entered blocking state
Mar 9 18:10:10 Tower kernel: docker0: port 1(veth619de24) entered forwarding state
Mar 9 18:10:11 Tower avahi-daemon[8233]: Joining mDNS multicast group on interface veth619de24.IPv6 with address fe80::805e:72ff:fe2d:5e39.
Mar 9 18:10:11 Tower avahi-daemon[8233]: New relevant interface veth619de24.IPv6 for mDNS.
Mar 9 18:10:11 Tower avahi-daemon[8233]: Registering new address record for fe80::805e:72ff:fe2d:5e39 on veth619de24.*.
Mar 9 18:10:42 Tower kernel: docker0: port 1(veth619de24) entered disabled state
Mar 9 18:10:42 Tower kernel: veth88d9518: renamed from eth0
Mar 9 18:10:43 Tower avahi-daemon[8233]: Interface veth619de24.IPv6 no longer relevant for mDNS.
Mar 9 18:10:43 Tower avahi-daemon[8233]: Leaving mDNS multicast group on interface veth619de24.IPv6 with address fe80::805e:72ff:fe2d:5e39.
Mar 9 18:10:43 Tower kernel: docker0: port 1(veth619de24) entered disabled state
Mar 9 18:10:43 Tower kernel: device veth619de24 left promiscuous mode
Mar 9 18:10:43 Tower kernel: docker0: port 1(veth619de24) entered disabled state
Mar 9 18:10:43 Tower avahi-daemon[8233]: Withdrawing address record for fe80::805e:72ff:fe2d:5e39 on veth619de24.
Mar 9 18:10:46 Tower kernel: docker0: port 1(vethccc1e30) entered blocking state
Mar 9 18:10:46 Tower kernel: docker0: port 1(vethccc1e30) entered disabled state
Mar 9 18:10:46 Tower kernel: device vethccc1e30 entered promiscuous mode
Mar 9 18:10:55 Tower kernel: eth0: renamed from veth3feaeb3
Mar 9 18:10:55 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethccc1e30: link becomes ready
Mar 9 18:10:55 Tower kernel: docker0: port 1(vethccc1e30) entered blocking state
Mar 9 18:10:55 Tower kernel: docker0: port 1(vethccc1e30) entered forwarding state
Mar 9 18:10:57 Tower avahi-daemon[8233]: Joining mDNS multicast group on interface vethccc1e30.IPv6 with address fe80::981c:6cff:fe1f:a231.
Mar 9 18:10:57 Tower avahi-daemon[8233]: New relevant interface vethccc1e30.IPv6 for mDNS.
Mar 9 18:10:57 Tower avahi-daemon[8233]: Registering new address record for fe80::981c:6cff:fe1f:a231 on vethccc1e30.*.
Mar 9 18:11:24 Tower kernel: docker0: port 1(vethccc1e30) entered disabled state
Mar 9 18:11:24 Tower kernel: veth3feaeb3: renamed from eth0
Mar 9 18:11:28 Tower avahi-daemon[8233]: Interface vethccc1e30.IPv6 no longer relevant for mDNS.
Mar 9 18:11:28 Tower avahi-daemon[8233]: Leaving mDNS multicast group on interface vethccc1e30.IPv6 with address fe80::981c:6cff:fe1f:a231.
Mar 9 18:11:28 Tower kernel: docker0: port 1(vethccc1e30) entered disabled state
Mar 9 18:11:28 Tower kernel: device vethccc1e30 left promiscuous mode
Mar 9 18:11:28 Tower kernel: docker0: port 1(vethccc1e30) entered disabled state
Mar 9 18:11:28 Tower avahi-daemon[8233]: Withdrawing address record for fe80::981c:6cff:fe1f:a231 on vethccc1e30.
Mar 9 18:11:34 Tower kernel: docker0: port 1(vethba81011) entered blocking state
Mar 9 18:11:34 Tower kernel: docker0: port 1(vethba81011) entered disabled state
Mar 9 18:11:34 Tower kernel: device vethba81011 entered promiscuous mode
Mar 9 18:11:34 Tower kernel: docker0: port 1(vethba81011) entered blocking state
Mar 9 18:11:34 Tower kernel: docker0: port 1(vethba81011) entered forwarding state
Mar 9 18:11:34 Tower kernel: docker0: port 1(vethba81011) entered disabled state
Mar 9 18:11:45 Tower kernel: eth0: renamed from veth91e6c6f
Mar 9 18:11:45 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethba81011: link becomes ready
Mar 9 18:11:45 Tower kernel: docker0: port 1(vethba81011) entered blocking state
Mar 9 18:11:45 Tower kernel: docker0: port 1(vethba81011) entered forwarding state
Mar 9 18:11:46 Tower avahi-daemon[8233]: Joining mDNS multicast group on interface vethba81011.IPv6 with address fe80::1048:70ff:fe09:14f4.
Mar 9 18:11:46 Tower avahi-daemon[8233]: New relevant interface vethba81011.IPv6 for mDNS.
Mar 9 18:11:46 Tower avahi-daemon[8233]: Registering new address record for fe80::1048:70ff:fe09:14f4 on vethba81011.*

  • Author
43 minutes ago, gunnarh said:

Have been running Valheim server for 5 month without problem but that is one thing that bothers me. When i check Unraid log i get this in the log and have checked it is from Valheim docker. Is any way to stop this?

Are you sure this is from the Valheim container? This happens usually when a container restarts.

1 hour ago, ich777 said:

Are you sure this is from the Valheim container? This happens usually when a container restarts.

 Yes i am sure, I have stop all containers and it still happens and when i stop Valheim it stops. And if i run all the containers but not Valheim it will not happend.

  • Author
51 minutes ago, gunnarh said:

Yes i am sure, I have stop all containers and it still happens and when i stop Valheim it stops. And if i run all the containers but not Valheim it will not happend.

@bonienl do you have a clue why this happens? It seems like the container restarts but it doesn't restart, see this post:

 

@gunnarh does this also happen when no one plays on the container? Is this maybe caused when someone connects to the Valheim server? How often do you get this message? Are you sure that the container is running and you actually can connect to the game server?

On 9/12/2019 at 3:41 PM, ich777 said:

Totaly doable but you need a separate account for the serverfiles to download or you disable your steam guard if you enabled it (steam recommends to create a dedicated account for all your dedicated servers).

I will look into that also.

Thank you for saying you'd look into this Natural Selection 2 docker, having a separate steam account is not a problem for me to setup... I dont totally follow on the next part (about how to implement rank/unranked) but if you know how to implement an option for ranked/unranked server I would be grateful :)

 

I was just checking in to see how things might be going with this? 

Edited by Malus

  • Author
1 hour ago, Malus said:

Thank you for saying you'd look into this Natural Selection 2 docker, having a separate steam account is not a problem for me to setup...

Looks like I forgot about this for a long time... :P

 

I actually stopped creating containers for games that I personally don't own because giving support for such containers is a real nightmare for me.

Hey, is GMod working for anyone?

The fresh install doesn't work for me. Unraid is in my local network but I can't find the server. Here is my log:

---Checking if UID: 99 matches user---
---Checking if GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1646806219
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...Connectivity test: result=Connected, in progress=0
OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
---Validating installation---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1646806219
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...Connectivity test: result=Connected, in progress=0
OK
Waiting for client config...OK
Waiting for user info...OK
[33;1mPlease use force_install_dir before logon!
[0m Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x5) verifying install, progress: 0.04 (1499847 / 3991352074)
Update state (0x5) verifying install, progress: 1.64 (65403545 / 3991352074)
Update state (0x5) verifying install, progress: 3.55 (141622030 / 3991352074)
Update state (0x5) verifying install, progress: 6.34 (253127208 / 3991352074)
Update state (0x5) verifying install, progress: 9.04 (360769911 / 3991352074)
Update state (0x5) verifying install, progress: 12.61 (503439165 / 3991352074)
Update state (0x5) verifying install, progress: 15.31 (610878565 / 3991352074)
Update state (0x5) verifying install, progress: 17.62 (703337460 / 3991352074)
Update state (0x5) verifying install, progress: 22.88 (913312076 / 3991352074)
Update state (0x5) verifying install, progress: 28.44 (1135032759 / 3991352074)
Update state (0x5) verifying install, progress: 29.37 (1172271019 / 3991352074)
Update state (0x5) verifying install, progress: 34.40 (1373135250 / 3991352074)
Update state (0x5) verifying install, progress: 39.58 (1579815734 / 3991352074)
Update state (0x5) verifying install, progress: 43.34 (1729681595 / 3991352074)
Update state (0x5) verifying install, progress: 44.93 (1793477364 / 3991352074)
Update state (0x5) verifying install, progress: 50.91 (2032000594 / 3991352074)
Update state (0x5) verifying install, progress: 54.05 (2157304261 / 3991352074)
Update state (0x5) verifying install, progress: 56.59 (2258539623 / 3991352074)
Update state (0x5) verifying install, progress: 59.27 (2365610280 / 3991352074)
Update state (0x5) verifying install, progress: 60.94 (2432476885 / 3991352074)
Update state (0x5) verifying install, progress: 65.32 (2607197080 / 3991352074)
Update state (0x5) verifying install, progress: 69.65 (2780101527 / 3991352074)
Update state (0x5) verifying install, progress: 73.32 (2926547926 / 3991352074)
Update state (0x5) verifying install, progress: 75.71 (3021669394 / 3991352074)
Update state (0x5) verifying install, progress: 78.82 (3146165761 / 3991352074)
Update state (0x5) verifying install, progress: 83.37 (3327746793 / 3991352074)
Update state (0x5) verifying install, progress: 86.79 (3464270974 / 3991352074)
Update state (0x5) verifying install, progress: 90.24 (3601637851 / 3991352074)
Update state (0x5) verifying install, progress: 93.80 (3743996820 / 3991352074)
Update state (0x5) verifying install, progress: 98.67 (3938218398 / 3991352074)
Success! App '4020' fully installed.
---Prepare Server---
---Server ready---
---Start Server---
Auto detecting CPU
Using default binary: ./srcds_linux
Server will auto-restart if there is a crash.
tcmalloc: large alloc 4288077824 bytes == (nil) @
tcmalloc: large alloc 4288077824 bytes == (nil) @
Setting breakpad minidump AppID = 4000
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
tcmalloc: large alloc 4288077824 bytes == (nil) @
Setting breakpad minidump AppID = 4000
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 6 milliseconds to initialize
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.

 

Is there anything to do before the server is working in LAN?

thx

  • Author
10 minutes ago, ra4e1 said:

The fresh install doesn't work for me.

Do you have a Cache drive installed in your Server?

Habe you changed anything in the template?

 

It looks like everything should work as expected, how did you try to connect to the container?

10 minutes ago, ich777 said:

Do you have a Cache drive installed in your Server?

Currently not, but I have one laying around.

 

11 minutes ago, ich777 said:

Habe you changed anything in the template?

I've tried various changes, but also without.

 

13 minutes ago, ich777 said:

It looks like everything should work as expected, how did you try to connect to the container?

I tried to find the server in the LAN server list but also tried to connect via IP:port

  • Author
2 minutes ago, ra4e1 said:

I've tried various changes, but also without.

What changes? Have done anything to the port?

 

2 minutes ago, ra4e1 said:

Currently not, but I have one laying around.

To what is the Game File path set?

Are the game files split across multiple disks?

5 minutes ago, ich777 said:

What changes? Have done anything to the port?

I didn't touch the ports (27015) or the paths. Should I?

 

I tried validate installation and different game parameters.

 

4 minutes ago, ich777 said:

To what is the Game File path set?

Are the game files split across multiple disks?

SteamCMD: /mnt/user/appdata/steamcmd

ServerFiles: /mnt/disk1/appdata/garrysmod

 

I only have one disk and a paraty drive

  • Author
Just now, ra4e1 said:

I didn't touch the ports (27015) or the paths. Should I?

No, of course not!

 

I now tried it now on my own and it works flawlessly:

1.thumb.png.8695bcb9648e2206c1e854883f2bcb4d.png

2.png.72bc2c95314d6d4eccbfc15691e68aa8.png

 

...and here is the log: garrysmod.txt

 

Please keep in mind, I didn't touch a single thing in the container template and it worked right OOB.

 

On what Unraid version are you?

  • Author
Just now, ra4e1 said:

I tried validate installation and different game parameters.

Please turn off validation, validation will cause a longer start because it validates the files on every start from the game.

 

I've now also pushed a update to the container, only a modernization and update thing.

(the above test was with the old version that you are running, the new container also runs fine)

 

Is the container on the same sub net as you local computer?

5 minutes ago, ich777 said:

Is the container on the same sub net as you local computer?

Yes

 

13 minutes ago, ich777 said:

On what Unraid version are you?

6.9.2

 

I will try the updated version

  • Author
8 minutes ago, ra4e1 said:

6.9.2

Then it should work right OOB like it did in my case.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.