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.

45 minutes ago, ich777 said:

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.

Yes it shows up on the server list (public) with my public ip, my friend tried to join but had the same issue where it was infinitely connecting. As for Port forwarding I setup internal and external tcp and udp for 9600 and 8081

Edited October 24, 20241 yr by sean1325

27 minutes ago, sean1325 said:

8081

Please only try to forward port 8081 TCP not both TCP and UDP.

 

What are those other ports for Assetto Corsa, for the base game you only need 9600 both TCP & UDP and 8081 TCP.

If you don't want to share the web interface directly to the world wide web then don't share the port or better speaking don't forward it in your router.

 

Do you have anything in the logs?

1 minute ago, ich777 said:

Please only try to forward port 8081 TCP not both TCP and UDP.

 

What are those other ports for Assetto Corsa, for the base game you only need 9600 both TCP & UDP and 8081 TCP.

If you don't want to share the web interface directly to the world wide web then don't share the port or better speaking don't forward it in your router.

 

Do you have anything in the logs?

The other ports where when I was trying to work with those, and if I remember correctly I only had 8081 tcp and had the same issue. I will remove the other ports and leave it as you mentioned. As for the log which one do you need? (I'm kinda new to unraid and docker stuff like about 5 months now but learning quick haha) and I showed the port forward to know if I had anything wrong. Plus I'm kinda visual on things.

1 hour ago, ich777 said:

Do you have anything in the logs?

in the session logs under appdata > assettocorsa > logs > session, i get log spam from <"Error listening %!e(syscall.Errno=22)">

 

if that's the log you wanted to look into.

4 hours ago, sean1325 said:

in the session logs under appdata > assettocorsa > logs > session, i get log spam from <"Error listening %!e(syscall.Errno=22)">

 

if that's the log you wanted to look into.

i think i fixed it by re installing it and copying the config stuff then restarting the docker. Thanks for your time and help continue your awesome work on this project. it loads right away in lan and with mods added everything works

21 hours ago, ich777 said:

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.

I'm not sure if I'm doing something wrong but I haven't been able to get the container working since last uninstalling /reinstalling. The server will show in game but any attempts to join fail.

I also get various errors in the logs depending on whether I try reconfiguring fresh, with saved backups, or with just config backups.

This may be a more general question to be asking here but is there a way I'm unaware of to totally delete a containers files from unraid? When I reinstall it doesn't take long to boot the server like you mention it should by reinstalling the game. Seems like the game must still be installed. I keep deleting the contrainer and image as well as deleting the appdata folder through console with rm -r "...appdata/longvinter/" but when I reinstall it still seems to remember my settings, drops the container right in the same folder I had it in previously. I'm thinking my issue might be that everything isn't getting deleted but I'm not sure how to wipe it any more cleanly than that.

Edited October 25, 20241 yr by ANJ_

11 hours ago, ANJ_ said:

I'm not sure if I'm doing something wrong but I haven't been able to get the container working since last uninstalling /reinstalling. The server will show in game but any attempts to join fail.

Any more information on that, I just tried a completely fresh install and it is working perfectly fine.

 

The default port is still 27016 and the password is also for the default installation Docker

 

11 hours ago, ANJ_ said:

I also get various errors in the logs depending on whether I try reconfiguring fresh, with saved backups, or with just config backups.

I assume because that's now because I'm using the SteamCMD version which is probably a bit more verbose.

 

11 hours ago, ANJ_ said:

This may be a more general question to be asking here but is there a way I'm unaware of to totally delete a containers files from unraid?

Delete the container, delete the directory from the container from your appdata directory, reinstall a fresh copy from the CA App.

 

When deleting the data it always depends to what your appdata share is set and if you use the FUSE path /mnt/user/appdata/... or the real path eg: /mnt/cache/appdata/... in the template.

 

If you use /mnt/cache/appdata/... just make sure to delete the directory from your cache drive, if you are useing /mnt/user/appdata/... and the Mover is set to move the data to the Array you should make sure to delete the folder for the container from /mnt/user/appdata/...

 

Here is a screensho t where you can see that I'm connected to the container:

 

Did you yet try to create a new server without an old save game? Maybe the GitHub version and the SteamCMD version are not compatible (but I don't think that's the case).

4 hours ago, ich777 said:

Any more information on that, I just tried a completely fresh install and it is working perfectly fine.

 

I'll keep fiddling around, it must be something I'm missing, just strange I can't seem to make a new server work off a fresh install but I'll try at it again soon here. Thanks for the help

Hi folks, I had a Satisfactory server running over a year ago when it was early access.  I recently tried to start it up again now that the game is released, and while it appears to have updated properly, I am having an issue connecting to the server with the client.  After adding a server with the my LAN IP and default port, the client shows a server with low ping, it shows the "Server Name Pending" and "not authenticated" as well as "Failed to Connect to the Server API".  Unfortunately I don't remember if there were other steps I took to get it running originally.  Can anyone shed some light on this?

49 minutes ago, Waltm said:

Can anyone shed some light on this?

Please read this post:

 

 

I think it would be best to start over since you need to do some kind of migration IIRC, this is now necessary if you want to port over a save game from beta to release but don't quote me on that.

2 hours ago, ich777 said:

I think it would be best to start over since you need to do some kind of migration IIRC, this is now necessary if you want to port over a save game from beta to release but don't quote me on that.

 

Starting fresh worked.  It even seems like there are fewer ports with the new install than there were on the old one.  Thank you for your help!

 

Hello, i've tried asking on the lancache discord about this, i'll try asking here too since no one could help me and this is driving me crazy. So basically all started when i ran out of space on my cache drives, what i did was (probably not the smartest idea) a " rm /cache/path/ -r" and rebuilt the containers, since there were some games i'm not playing anymore and i wanted to delete the cached data and start over with the prefill. Since then on BattleNet and Epic there's an error everytime (both the prefill and direct download from a client) try to connect, on Steam what i see is that it manages to "connect" to the servers but the download speed is so low, we're talking about tens of bits when it spikes up and the falls down to zero and the cache is not getting filled as the occupied space on the share stays the same. The error that i'm getting on Epic and BN is the following:
Unexpected download error : An error occurred while sending the request. Skipping app... 
I have the dns configured so the clients have the lancache one as primary dns that has an upstream connection to my pi hole. I've tryed reverting the order, bypassing pihole entirely, but nothing helped. What i could see in the logs were a mix of error 504, in the stream error.log, then there were "access denied" to the cache files (there was none, as it was empty), then time outs on the requests like this one:
"

*654 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.67, server: , request: "GET /depot/431241/chunk/ff9cf8205553e9ec0c8f396a67a153b5931f331f HTTP/1.1", upstream: "http://127.0.0.1:3128/depot/431241/chunk/ff9cf8205553e9ec0c8f396a67a153b5931f331f", host: "cache6-fra1.steamcontent.com"

"
.
in one of the dozens of reboots/rebuilds of the lancache, lancache-dns and prefill containers my log files turned into this:

So i can't access them anymore, at least i don't know how to.
If there's any test/command to run/check i can do i would really appreciate anyone's help because i feel like i've done everything i could to get it to work but sadly with no avail... I am not very skilled in the docker side of things but i'm pretty sure all my containers are set up correctly as well...

Edited October 29, 20241 yr by Bahamut___
additional details

59 minutes ago, Bahamut___ said:

he error that i'm getting on Epic and BN

So I assume we are talking about LANCache-Prefill correct?

If so you are in the wrong support thread, you can always get to the correct support thread by going to the Docker page, click on the container icon and Support.

I would recommend that you create an issue in the GitHub repository from @tpill90 over here for Epic and over here for BattleNet.

 

However I can't reproduce this over here so I suspect a network/configuration issue.

 

1 hour ago, Bahamut___ said:

in one of the dozens of reboots/rebuilds of the lancache, lancache-dns and prefill containers my log files turned into this:

This is caused because you've deleted files when the container was most certainly running, please always stop the container first and then do your edits/removal from files otherwise you will be left with those files.

 

1 hour ago, Bahamut___ said:

but i'm pretty sure all my containers are set up correctly as well...

In no offense, you are doing pretty risky stuff when doing a manual remove from all folders (or a folder) in your cache directory which I would most likely never recommend.

 

As said, please always stop containers before doing any edits/removing files from it, just as an example, you also don't take out the RAM without shutting down your computer...

i wasn't sure which one was the most accurate but yes, it's both prefill and lancache itself that don't work properly at this point, the prefill not being able to start a download, i believe, is most likely a consequence.
I always check that the containers are stopped before doing operations like these but in the process i must've forgotten... i'm going to try to start over and reinstall everything from scratch and learn from my mistakes! but if there's a problem on my network configuration i have the feeling this could not fix the issue so i would like to investigate first and see where the problem(s) is(are).
I appreciate you pointing out that this is not a safe procedure and i felt like it wasn't as well but i couldn't find another way to achieve what i wanted to and went down that way...
In the previous message i've forgot to mention that if i set the dns in the client to the google one (8.8.8.8) the download starts and proceed regularly, same if i only use my Pi Hole DNS so i guess there's something messed up in the Lancache dns or in the Lancache monolithic container.

Edited October 29, 20241 yr by Bahamut___

2 hours ago, Bahamut___ said:

lancache

Sorry I don't have a container for LANCache, I just provide LANCache-Prefill.

 

2 hours ago, Bahamut___ said:

so i guess there's something messed up in the Lancache dns or in the Lancache monolithic container

Most likely not because if you install them from scratch nothing can be messed up.

 

I assume something on your network is blocking the IP/Hostnames that it want's to connect to, however as this seems to be an issue with your network and is most likely not related to LANCache-Prefill I can't do/help much.

Valheim Dedicated Server won't start 

 

Since Valheim came out I've been hosting two Valheim servers simultaneously with no problem in unraid. Well it's been many months since we've played and I went to start the servers today only for them to not update at all. Since I have backups I deleted the entire container from appdata and reinstalled the image from the app library. I left all the container parameters as-is, with the exception of the network, and the container hangs after posting an API error in the log. No matter how long I leave the log open and the container running, the server never starts. 

 

 

I'm on 6.12.13 with no other changes since successfully running servers in the past. I've tried some suggestions from others on this tread (deleted all files in appdata/Valheim, except for .config and backup), to no luck. 

 

Thanks!

9 minutes ago, RedRambo said:

and the container hangs after posting an API error in the log

The container is actually started and waiting for connections, you ight never seen this message before because you had no issues and never opened the log.

 

9 minutes ago, RedRambo said:

the server never starts

How much system resources does the container consume (Advanced View on the Docker page)?

 

9 minutes ago, RedRambo said:

deleted all files in appdata/Valheim, except for .config and backup

Have you yet tried to delete the entire contents and put your backups somewhere safe so that you can install a real fresh copy from the container and yes you will see the same message.

 

Do you leaf the name/password in the template as is or did you change it?

Please keep in mind that I wouldn’t recommend using special characters for the password and name.

I did managed to get everything working and backups restored on a new install! 

 

7 hours ago, ich777 said:

The container is actually started and waiting for connections, you ight never seen this message before because you had no issues and never opened the log.

When creating the new container, I failed to set the 'Debug Log Output' to true, as I have in the past... I've monitored the logs a lot to check for incompatible mod versions, etc when people connect to the server. 

 

Thank you for your reply. This is an example of why I shouldn't take on these projects so late at night! haha