Androidz

So I have WSUS caching setup and it works for about 4 hours and then randomly stops working. Dockers are up and running, but I can't see anything obvious in the logs. When I created the docker I set my upstream DNS to my pfsense router, so perhaps that has something to do with it. Anyone have any ideas?

@Dred88 - That would be awful! Does anyone know if it possible to forward DNS from pfsense -> steamcache-dns -> out (or back to pfsense)?

@Dred88 - No, it's all inclusive you only use steamcache-dns IP and it handles everything (Steam, Windows Updates, Origin, etc)

@Sam Katoen - GOD BLESS YOU! This is working!!! For those of you wanting to cache Windows updates see Sam's reply - https://linustechtips.com/main/topic/962655-steam-caching-tutorial/?page=2&tab=comments#comment-11672873 TL;DR -e WSUSCACHE_IP=192.168.1.55 \

@Dred88 - You would point to steamcache-dns IP.

I have steam cache running but its not actually caching. Not going to spend anymore time on it since my main goal was Windows Updates. If you end up getting that working please let me know. Thank you

@Larklen - Thank you for the reply. You are correct, without Windows cache steamcache-dns works fine. Unfortunately my goal was caching windows updates and nothing else. @Unieveth - See Larklen's reply. Looks like Windows cache is broken. Perhaps someone can find a fix?

I have tried this on three VM's with no success. I first started with CentOS as that is my flavor, no mas. So then I decided to try exactly what the tutorial says and used 18.04 desktop, that also failed. I raged quit and moved on to today..... Today I decided to try again as I thought I may have missed something in the tutorial which may be incorrect. It says you require an IP for each cache service, but if only caching one service you can "skip". So I believe what the tutorial means is that you need an IP (separate from host) for each cache, regardless of using one cache service or multiple. Is this correct? So I setup a new 18.04 LTS host with multiple IP's and again I run into the same issue and that is steamcache-dns constantly restarting. I believe the issue is related to port 53, so I tried to change the port however steamcache-dns always wants port 53. I use DNS Resolver in pfsense which uses port 53 so I believe that is where the problem is, however I haven't tried altering pfsense at this time. pfsense: The port used for responding to DNS queries. It should normally be left blank unless another service needs to bind to TCP/UDP port 53. Docker: sudo docker run \ > --restart unless-stopped -d \ > --name steamcache-dns \ > -p 192.168.1.26:55:55/udp \ <- This is where I tried binding to port 55 instead, however no matter what it wants to use port 53 > -e UPSTREAM_DNS=192.168.1.1 \ > -e WINDOWSCACHE_IP=192.168.1.27 \ > steamcache/steamcache-dns:latest sudo docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8ec9096f75da steamcache/steamcache-dns:latest "bash /scripts/boots…" 3 seconds ago Up 1 second 192.168.1.26:53->53/udp steamcache-dns 1f4d9897f9d8 steamcache/sniproxy:latest "sniproxy -f" 21 minutes ago Up 18 minutes 0.0.0.0:443->443/tcp sniproxy 58ee1b56c65a steamcache/generic:latest "/scripts/bootstrap.…" 27 minutes ago Up 18 minutes 192.168.1.27:80->80/tcp windows-cache 5 seconds later.... 8ec9096f75da steamcache/steamcache-dns:latest "bash /scripts/boots…" 6 seconds ago Restarting (1) Less than a second ago steamcache-dns Questions: 1. Is there anyway to bind steamcache-dns to something other than 53? 2. Is opening port 53 required on firewall? This is not mentioned in the tutorial. 3a. Anyone with pfsense using DNS Resolver (53) try running this? 3b. Did you switch the pfsense DNS Resolve port?

Enter me please! That headset matches my computer desk, would look amazing!

Anyone else have any ideas?

It's definitely not automatically sleeping. If I manual sleep everything shuts off (motherboard led's, fans, etc) when I resume I am prompted for password. If I set the sleep timer to 10 minutes nothing happens. "also Using a fan directly connected to the PSU will not let the hybrid sleep feature work as intended so that might be the problem." - Not sure what you mean by this?

I recently saw the video regarding sleep/hibernation and thought, yeah I should do that. I leave my PC on 24/7/365 but I do leave it unattended often, so why not use sleep and save some power. Then I remember back to Windows 7 that auto sleep never worked for me, and here I am years later on 8.1 and I have the same exact issue. Sleep or Hibernate simply will not work AUTOMATICALLY. It works FINE if I do it manually, however auto just never seems to work. System will go into and recover without issue from sleep. I have tried adjusting various settings, checking bios, disable network power options, still the system will not sleep automatically. I really feel like this issue is related to some sort of bios power option, but I am not sure which. Not sure what else it could be. Any help would be much appreciated. Below are my system specs. PC Specs: Mobo: Rampage V Extreme x99 CPU: 5820K @ 4.5GHZ RAM: Kingston HyperX DDR4-3000 @ 3GHz GPU1: eVga GTX 980 SC @ 1600/7800 GPU2: eVga GTX 980 SC @ 1600/7800 HDD: Samsung 1TB SSD HDD: 4x4TB WD Black Enterprise on Adaptec 512MB RAID 10 PSU: Corsair HX1000 Sound: Sound Blaster Z Case: Corsair Obsidian 800D Peripherals: LG 27" Monitor Corsair K70 Mechanical Keyboard Logitech G502 Mouse Sennheiser G4ME ONE Headset XBOX 360 Wireless Controller