cheesemarathon

Yes, this is a bit of a bug, it may take several downloads to fully cache some games. @mlebjerg is currently working on moving the container over to a completely new caching system which should fix this.

If it's the first time you have downloaded a game through the cache then "MISS" is correct. "MISS" just means it was unable to download the file from the cache, so will get it from the steam servers instead. When the download is complete and you reinstalled the game, you would get mostly "HIT" in the logs, as the files can now be found in the cache.

Ah yes! Windows is funny like that. You think it would only use the second server if the first failed, but no, it will pick one randomly!

@mlebjerg a question best answered by you I think

I don't think it binds unless you use https for your unraid UI but I changed mine to be on the safe side

This should be an easy fix. By default the unraid UI is on port 80 but steamcache must run on port 80. To fix this, stop steamcache, then in unraid settings change the port to 85 (any port not in use will work). Then restart steamcache and you should be all good. I cant remember exactly where in the settings the port number setting is but I'm sure you'll find it

Have you followed the installation instructions? They were recently updated. When you browse to http://<unRAID-IP>:4180 you should see: If this is not the case, can you post the logs from the container. Hopefully, that will shed some light on the issue.

I'm not an expert in system stats but by the looks of things, your system usage is high because of IO wait. This is the system waiting for input/output operations to complete. If in netdata on the right hand side you click on steamcache, I would imagine you will see nearly 100% cpu usage on this container. To fix this there are several things you can look at. One of your disks may have an issue with it, slowing down read/write operations, you may also be running low on RAM in the system. I have not seen this issue before with Steamcache so I don't think that it is anything specific to steam cache causing an issue, it has just highlighted the problem. When building a NAS IOWait is an issue because most the of the applications you use a NAS for will at some point perform large read/write operations to disks. So I suggest that you do some googling to find a solution as there is no deffinitive fix for this. If you do need more help however, just ask! 🙂

Hmm that is very strange! If that first screenshot was taken at the same time as your ran htop then I would say that the dashboard is doing something wrong. I suggest you install Netdata from community applications. This will show you a lot of useful stats for diagnosing issues. Overall statistics and stats are broken down to individual containers.

Thanks, will do!

Hmm, I'm sorry to hear that. Are you able to post any of your logs where the error occurs? I won't pull the latest update, for now, see if we can compare our setups!

If your updating there should be no issues. If it's a fresh install then see the updated instructions here!

The update is live!

Yes! I have moved my local install over to the pusher docker image with no breaking changes. I just have a slight bug where I get redirected to the wrong page when auth fails. When I have that sorted I'll update the template!

You would have to pull the repo, build the docker image from the dockerfile and then change the repository name in the unraid ui to the tag you gave the image when you built it. That should work provided no breaking changes were made. But thats not super simple, so @mlebjerg how far have you got with pulling those changes into the main repo?

It looks like this is something that has come up before. There is nothing official supporting fail to ban, however, login attempts are written to the logs. So you should be able to use the logs with fail2ban. This is discussed in detail here. I have not set this up myself and have little experience with fail2ban, but shout if you need some help. The GitHub issue discusses setting it up with docker but not UnRAID which may make it harder or easier in place. I don't know, but do let me know how you get on. I can always create some instructions for others if we get this working. Good luck!

Thanks mlebjerg 🙂

@mlebjerg Have you seen this message? Something you can work on?

Hi, sorry I haven't had time to look at this, however, @mlebjerg is the expert and maintainer of this version of the container so I shall message him and hopefully, he can add the option

Thanks for all the info. I will spin up my instance of steamcache when I get home from work, as i'm unsure what the issue is here.

In your windows pc dns settings I would not set the secondary DNS. Although you might think it would only use that if the first fails, that is not always the case depending on the application. Some times it will skip the first or just randomly chose one of the two. If you only set one, there is only one it can use. I havn't used steamcache in a bit. I'll spin up my instance when I get home tonight and see if i'm having any issues.

Hey! Year very nearly there. There is just one error in your config. The "LANCACHE_IP" setting wants to be the same IP as you set in the "Fixed IP" setting. So in your case both should be 192.168.1.75 Then you should be good to go. That command you run will then output the logs from the container and you will see the cache working.

Ok, background knowledge time. Docker containers run in their own self-contained environment. In order to get shell access to them you need to run the command: docker exec -it <container-name> <command> This will run the command you place in <command> in the container you specify. In unRAID you can also click the console button on the container you want, and this will open a console window in the container you specify. unRaid is effectively running the following command: docker exec -it <container-name> /bin/bash Then you can run any command you like and it will execute in then container. Therefore, you have two options. One, open a terminal window connected to your unRAID server and run: docker exec -it SteamCacheBundle tail -f /data/logs/access.log Here you can see you container name is "SteamCacheBundle" and the command is "tail -f /data/logs/access.log" Or you can open the unRAID GUI, click on the console button for the SteamCacheBundle container and then in the new window run: tail -f /data/logs/access.log I hope this clears things up for you

Head to the Docker page in the unRAID GUI. Click on the icon for Steam Cache Bundle. Click "Console". In the new window that opens type then hit enter. You should then be able to continue with the instructions. If it mentions running again, do as I have instructed here again.

This is not fixed yet however the issue is being looked into. There does seem to be a fix for now. Add the environment variable "DISABLE_WSUS" and set it to "true". The issue is being tracked here: https://github.com/uklans/cache-domains/issues/39