cheesemarathon

Ok, don't worry about the colour of the logs. White is correct. The log script has changed. Your logs look perfect btw. So it still looks like a permissions issue. It looks like the cache folder is owned by the user 100. Mine is owned by root. Try the following command to fix this chown -R root:root /mnt/user/steamcache Make sure you remove that second DNS entry on your gaming machine before you test again.

Run the following command chmod -R 777 /mnt/user/steamcache That will set the steamcache and all folders and files inside it to 777. I don't recommend leaving it as that but it will help identify if that's the issue. You can reduce the permissions with the same command once it's fixed.

@burningstarIV I'm sorry you're having problems. Thanks for all the info and screenshots. It really helps! First of all is the gaming machine not downloading anything? Or is there nothing appearing in your /mnt/user/steamcache folder. Or both? It looks like the containers are all set up correctly and that is proved by the logs. I would suggest that in the DNS container you reenable the services you have disabled. (remove the word true and leave blank). That might cause issues as I have not tested that function much. Also, check the permissions and ownership of the /mnt/user/steamcache folder. Mine is owned by root with 777 permissions. Change yours to match and see if that changes things. If none of that works we can have another look.

I'm having trouble using AMP to set up a tf2 server. Anyone know of some guides or want to help. The cube coders documentation is very lacking imo!

No problem I'm glad it's working Let me know if you have any more issues

@Oxide When using the command to check steamcache DNS. You need to supply it with the IP you assigned to the steamcache DNS container at install, not the IP of your unRAID server. So 192.168.0.99 in the command you posted above is wrong according to your example. Sorry if that's confusing. It's hard to explain with all the different IP addresses. Let me know if you need it explained further.

I'm assuming it's a restart that fixed it as well as I have just checked mine and the "ghost" images have gone.

I'm not sure it really matters. The location for the logs is set in the UI so you can call it whatever you want so long as you set the location correctly in the UI. I have mine set up working fine.

Hi there I'm having an issue where the docker update tab is showing containers that no longer exist. The containers in the image below that say "Unknown" for the image name no longer exist. They are not in the main docker list either. How does the plugin get its info on installed containers?

I have implemented the fix. It will take a couple of hours to appear in Community Applications. Once update in CA I suggest you remove your current container and re-add it from CA. Let me know if you have any more issues.

I hope not too. I've pulled it all from community applications myself now and it all still works perfectly as far as I can tell.

@nuhll@josywong@ColeBrodine Updated instructions can be found here Updates may take a couple hours to appear in community applications. If you try it, let me know how you get on. Thanks

nuhll, The issue you linked looks like it is only applicable to the steam cache image, not the generic cache image. This is explained here As the cause of this seems unclear still I'm not sure what to do. I think the fix would be beyond me anyway and I'm not the author of the image. I have not noticed this error as all folders in my cache are just numbered. Where are these nginx/dl1.steam.de/part1 folders located? Within your mounted cache directory?

@ColeBrodine@josywong@nuhll Hi Guys I have finally got the generic cache to work with origin. I'll be updating the containers and editing the instructions on my blog shortly. As a heads up, it does require changing the ports unRAID runs on. Hopefully, you can deal with that. I'll post here again when it's all ready!

I have the same issue as you. I have seen your issue on Github and added to it to try to find a solution.

8.5.0 is now available

I'm not the creator of this docker image. I just created and uploaded the template so we could use it easily in unRAID. However, I have just created an issue on Github asking why there is not an 8.5.0 image available yet. Hopefully, we will get a response soon. Thanks for letting me know it still hadn't been updated

Ok, I have managed to cause a crash when renaming as well now. Your right it's an error in 8.4.0. Issue found here. It is fixed in version 8.4.1 and version 8.5.0 was released a few hours ago. The docker image should be updated soon, I imagine as soon as the automated build has completed. This should fix the issue.

Hi, I just removed my container and recreated it to force it to pull the latest version. The only thing that persisted was the config file. I tested before and after and the buttons seemed to work. I tried moving, renaming and opening and using the console. This was all done in chrome. Only thing I can think is make sure chrome/firefox are up to date and then delete the container (including image) and then delete the cloudcmd folder in your appdata folder. After this, you can recreate the container from community applications. There is an option to not display those buttons in the config file but if you can see them then they should work. But maybe your config has gone a little awry, hence the suggested refresh. If the issue persists after this I suggest that you open an issue here. Let me know how you get on.

This is hard for me to debug as I don't have a cache disk. However, I have tried moving files between shares and I don't get any issues where it doesn't move it. Therefore I'm assuming its either a permissions issue, most likely with the target directory, or some other issue that is limited to cache drives. To test the permissions theory I would create a blank file owned by 99 and group 100 and the same for a directory in a different location. Make sure the permissions on the file and directory are 777 to rule out lack of permissions and try to move the file to the new directory.

@senseiner Got a method to sort this. Edit the cloud commander container and in the "Extra Parameters" box enter -u 99:100 Click apply and now any changes or moves or creations should be made with the user nobody

@senseiner I have had a look at your request again and I believe this feature will require building into the docker image. I'm not the author of this container image, however, I have opened an issue on GitHub with the author to try and come up with a solution. I'll post updates here when necessary.

Should not be a problem. I'll attempt the changes later today.

@nuhll I have updated steamcache dns and added generic cache to community applications. All required variables should be easily edited now. I have written install instructions as well which are linked at the top of this thread. As for SNI Proxy. I am still working on a solution.

Sorry just noticed that I did the update wrong. A fixed version should be available in the next 2 hours.