Gohaun Posted October 25, 2020 Share Posted October 25, 2020 (edited) I cant seem to start the docker anymore. I turned the server off, so I could use the power supply to test some equipment that I got in. (New power supply then arrived a day later) I turned the server back on and everything came up but lancache bundle. I get execution error "error 403" I tried to look at the logs, and cant seem to find it. I havent looked at them since I got this setup months ago. Anyone run into this? I looked into the logs that unraid provide (top right side, multi line icon) and that doesnt seem to tell me what happened. Thanks for your time EDIT: After restarting my machine, I guess it didnt stick to the IP address I gave it, and the router gave the UNRaid server the IP that I had set aside for Lan Cache. I will need to see what I did wrong as its not a static IP, which is what I thought I set. Edited November 4, 2020 by Gohaun Quote Link to comment
der8ertl Posted October 27, 2020 Share Posted October 27, 2020 Hi, I don't know if anyone has successfully used the lancache-bundle docker for wsus, at least I couldn't find any "how to" so could anyone please help me? what are the correct settings for the clients? or do I even need to set something? I would assume, that I have to tell the windows client where the wsus server is (?) thanks in advance! 8ertl Quote Link to comment
c0rrre Posted October 30, 2020 Share Posted October 30, 2020 Hi, how fast is the docker container in ur systems? Ive got an 500 Mbit internet connection and im getting up to 60-65 MB/s without the cache. With cache I only get 1.5 MB/s I tried some of the tips in this topic but nothing worked for me. Can someone help? Thanks Quote Link to comment
Clutz450 Posted November 3, 2020 Share Posted November 3, 2020 Not sure if the main developer still proving any help here but I figured I'd ask here anyways. I was able to get this working when downloading and redownloading games from Steam. I had noticed that under more settings it mentions Nintendo and Sony (screenshot below). Now it says that I would have to change to option to true in order to disable caching for those. So does that mean it is enabled by default? I tried testing on my PS Vita and Nintendo Switch setting those up exactly like I did my computer for Steam but it appears that nothing is being cached when downloading from my PS Vita or Nintendo Switch. Is there anything additional I have to do to get this to work for gaming consoles like those or does this really only work for PC type games? Thank you. Quote Link to comment
Gohaun Posted November 4, 2020 Share Posted November 4, 2020 Clutz450 you are correct, it should be working by default. I dont have either of those systems to test, but I have set my router to point and hand out my lan cache IP. This way no matter what device gets onto my network, it will goto my lan cache ip first. Before doing this, I had to set everything in my network to point at my lan cache ip or it would not do anything. Hope that helps. Quote Link to comment
Gohaun Posted November 4, 2020 Share Posted November 4, 2020 der8ertl, before mine stopped working, I didnt have to do anything but set the first DNS request to my lan cache IP. I didnt check after setting my router to have my lan cache IP as the primary DNS IP. Image shows what I had before updating my network months ago, and I can confirm that worked as I forced my pc to updated with windows, then updated the other 4 windows 10 pcs in my house. hope that helps Quote Link to comment
Clutz450 Posted November 4, 2020 Share Posted November 4, 2020 3 hours ago, Gohaun said: Clutz450 you are correct, it should be working by default. I dont have either of those systems to test, but I have set my router to point and hand out my lan cache IP. This way no matter what device gets onto my network, it will goto my lan cache ip first. Before doing this, I had to set everything in my network to point at my lan cache ip or it would not do anything. Hope that helps. Thank you for the reply. The way I was doing it was I was manually setting the DNS to my lancache IP address on each device (PC, Switch, and Vita). It worked great on my PC for Steam games. It didn't seem to do anything for the Switch or Vita. How did you set it up through your router? Maybe I can try that next. I have an ASUS RT-AX58U if that helps any. Thank you. Quote Link to comment
Gohaun Posted November 4, 2020 Share Posted November 4, 2020 (edited) Clutz450 a quick search for "changing dns on ASUS RT-AX58U" will provide you where you can change the DNS addresses that your router looks for. You will need to update the details in the lan cache settings though as well. I would assume that you are using wifi for both PS and Switch, you might be limited by your wireless connection. So it doesnt look like its going faster, or that it is working. Are you checking on your UnRaid server to see if there is just outbound traffic from your server? You should also be able to see that when you remove a steam game and redownload it. Just the outbound should have a large transfer speed. Edited November 4, 2020 by Gohaun Quote Link to comment
TinsellyCone Posted November 4, 2020 Share Posted November 4, 2020 (edited) I got it installed just fine, but I am having issues. When I set it as the DNS server for my PC, it works as a DNS server and everything loads normally. Games download normally the first time, but it logs that it has that game cached, but doesn't cache anything. Next time I want to download that same game, it thinks it has it cached so it tries to pull from the cache, but there is nothing there, so it just doesn't do anything. Edit: I got it figured out - just needed a restart Edited November 7, 2020 by TinsellyCone Quote Link to comment
HidYn Posted November 14, 2020 Share Posted November 14, 2020 Hi Guys, Been using LanCache for over 6 months now and it's been fantastic for a family of 6. Today it seems to be broken all of a sudden. I get these errors in the nginx error log 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:11 [emerg] 2349#2349: still could not bind() 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:15 [emerg] 2370#2370: still could not bind() 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:18 [emerg] 2372#2372: still could not bind() 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: bind() to 0.0.0.0:443 failed (98: Address already in use) 2020/11/14 00:09:22 [emerg] 2374#2374: still could not bind() Any ideas? Quote Link to comment
Supermillhouse Posted November 14, 2020 Share Posted November 14, 2020 im having the same 443 binding problem as well, halp!!! Quote Link to comment
hammsandwich Posted November 15, 2020 Share Posted November 15, 2020 (edited) 22 hours ago, Supermillhouse said: im having the same 443 binding problem as well, halp!!! Same here after latest update. Same error messages filling up nginx error logs. Edited November 15, 2020 by hammsandwich Quote Link to comment
darkguitarist037 Posted November 16, 2020 Share Posted November 16, 2020 Looks like there were some updates to the upstream docker containers where they expose port 443 in the upstream container. I'm no docker expert so maybe this is why? New port expose in the PR from 3 days ago from `lancache-generic`: https://github.com/lancachenet/generic/pull/107/files which monolithic uses as a base. Is it as easy as removing the port expose from unraid's dockerfile/template? Also, I apologize if any of this is incorrect or out of line or inappropriate...I just have a vested interest in keeping this awesome docker up and running :) Quote Link to comment
Supermillhouse Posted November 16, 2020 Share Posted November 16, 2020 (edited) On 11/16/2020 at 9:05 PM, darkguitarist037 said: Looks like there were some updates to the upstream docker containers where they expose port 443 in the upstream container. I'm no docker expert so maybe this is why? New port expose in the PR from 3 days ago from `lancache-generic`: https://github.com/lancachenet/generic/pull/107/files which monolithic uses as a base. Is it as easy as removing the port expose from unraid's dockerfile/template? Also, I apologize if any of this is incorrect or out of line or inappropriate...I just have a vested interest in keeping this awesome docker up and running looks like the new gineric build has added ssl forwarding that sniproxy has been providing in this buindle, i think this is the clash, removing the sniproxy stuff from this bundle may resolve the errors. Confirmed, i have made a fork and removed the instalation of sniproxy and some other stuff and it looks to be working fine and i can still access https websites ok. Is there any other function sniproxy provided in the build except SSL forwarding? Edited November 17, 2020 by Supermillhouse Quote Link to comment
James_Darkness Posted November 17, 2020 Share Posted November 17, 2020 Quote I was planning on installing Lancache elk on a Ubuntu server vm in unraid but didn't want to start caching all over again is there anyway I can copy my cache it's about 1.5tb Quote Link to comment
Morikami Posted November 18, 2020 Share Posted November 18, 2020 On 11/16/2020 at 11:20 PM, Supermillhouse said: Confirmed, i have made a fork and removed the instalation of sniproxy and some other stuff and it looks to be working fine and i can still access https websites ok. So u managed to get the Docker working again? How did u do it? Quote Link to comment
Supermillhouse Posted November 18, 2020 Share Posted November 18, 2020 (edited) 4 hours ago, Morikami said: So u managed to get the Docker working again? How did u do it? Like I said, I made a fork of the repo on github, changed what needed to be changed and then created a docker image on docker hub which I then use in unraid. If this is a bit foreign to you, I advise not breaking your cache, I won’t be responsible if I have made a mistake some ware and something goes wrong for you. I am not going to advise you to do anything as this is not my docker template and I’m not going to hijack it, this was only to hopefuly get Josh on the right track from the gettgo. Edited November 18, 2020 by Supermillhouse Quote Link to comment
hammsandwich Posted November 18, 2020 Share Posted November 18, 2020 On 11/14/2020 at 5:56 PM, Supermillhouse said: im having the same 443 binding problem as well, halp!!! Looks like a new version was built off a fork to remove snip proxy. Any pull this yet and see if it works? I am not in front of a computer to test. Quote Link to comment
mdsloop Posted November 19, 2020 Share Posted November 19, 2020 i have the same 443 error and lancache is not working. can we roll back to older version( where do i find previous versions, and pull those in unraid docker?) or is waiting for a solution the only way? Quote Link to comment
hammsandwich Posted November 19, 2020 Share Posted November 19, 2020 As this docker relies on an older version of the upstream lancache dockers, and he is not tagging the builds or pulling tagged versions, I do not think this is currently possible. 1 Quote Link to comment
TrueImpulse Posted November 22, 2020 Share Posted November 22, 2020 (edited) Is there a way to delete cached data other then wiping the whole cache? I didn't notice the Twitch caching was a feature enabled by default. From what I understand this will cache any live streams you have watched on Twitch. I would like to delete all cached Twitch data that is taking up space. Thanks, Edited November 22, 2020 by TrueImpulse Quote Link to comment
Supermillhouse Posted November 23, 2020 Share Posted November 23, 2020 13 hours ago, TrueImpulse said: Is there a way to delete cached data other then wiping the whole cache? I didn't notice the Twitch caching was a feature enabled by default. From what I understand this will cache any live streams you have watched on Twitch. I would like to delete all cached Twitch data that is taking up space. Thanks, I believe it caches only twitch games, not the live streams, I watch a lot of twitch and I have never seen twitch in my access log, are you saying twitch is in your access log when you watch twitch streams? 1 Quote Link to comment
carvaletingpro Posted December 9, 2020 Share Posted December 9, 2020 Any ideas on this error i can't get the docker to restart Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='lancache-bundle' --net='br0' --ip='192.168.1.22' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'LANCACHE_IP'='192.168.1.22' -e 'DNS_BIND_IP'='192.168.1.22' -e 'CACHE_MEM_SIZE'='500m' -e 'CACHE_DISK_SIZE'='2000g' -e 'CACHE_MAX_AGE'='150d' -e 'UDP_PORT_53'='53' -e 'UPSTREAM_DNS'='1.1.1.1' -e 'USE_GENERIC_CACHE'='true' -e 'DISABLE_ARENANET'='' -e 'DISABLE_BLIZZARD'='' -e 'DISABLE_CITYOFHEROES'='' -e 'DISABLE_DAYBREAK'='' -e 'DISABLE_EPICGAMES'='' -e 'DISABLE_FRONTIER'='' -e 'DISABLE_HIREZ'='' -e 'DISABLE_NEVERWINTER'='' -e 'DISABLE_NEXUSMODS'='' -e 'DISABLE_NINTENDO'='' -e 'DISABLE_ORIGIN'='' -e 'DISABLE_RENEGADEX'='' -e 'DISABLE_RIOT'='' -e 'DISABLE_ROCKSTAR'='' -e 'DISABLE_SONY'='' -e 'DISABLE_STEAM'='' -e 'DISABLE_TESO'='' -e 'DISABLE_TWITCH'='' -e 'DISABLE_UPLAY'='' -e 'DISABLE_WARFRAME'='' -e 'DISABLE_WARGAMING'='' -e 'DISABLE_WSUS'='' -e 'DISABLE_XBOXLIVE'='' -v '/mnt/user/lancache':'/data/cache':'rw' -v '/mnt/user/appdata/lancache-bundle/log/named':'/var/log/named':'rw' -v '/mnt/user/appdata/lancache-bundle/log/nginx':'/var/log/nginx':'rw' 'josh5/lancache-bundle:latest' e56480e5e6e958ada81f2664ec12a773f44e220e1e4f3bba5e9780153256f7af /usr/bin/docker: Error response from daemon: Address already in use. The command failed. Quote Link to comment
iesou Posted December 20, 2020 Share Posted December 20, 2020 On 12/9/2020 at 4:18 PM, carvaletingpro said: Any ideas on this error i can't get the docker to restart Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='lancache-bundle' --net='br0' --ip='192.168.1.22' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'LANCACHE_IP'='192.168.1.22' -e 'DNS_BIND_IP'='192.168.1.22' -e 'CACHE_MEM_SIZE'='500m' -e 'CACHE_DISK_SIZE'='2000g' -e 'CACHE_MAX_AGE'='150d' -e 'UDP_PORT_53'='53' -e 'UPSTREAM_DNS'='1.1.1.1' -e 'USE_GENERIC_CACHE'='true' -e 'DISABLE_ARENANET'='' -e 'DISABLE_BLIZZARD'='' -e 'DISABLE_CITYOFHEROES'='' -e 'DISABLE_DAYBREAK'='' -e 'DISABLE_EPICGAMES'='' -e 'DISABLE_FRONTIER'='' -e 'DISABLE_HIREZ'='' -e 'DISABLE_NEVERWINTER'='' -e 'DISABLE_NEXUSMODS'='' -e 'DISABLE_NINTENDO'='' -e 'DISABLE_ORIGIN'='' -e 'DISABLE_RENEGADEX'='' -e 'DISABLE_RIOT'='' -e 'DISABLE_ROCKSTAR'='' -e 'DISABLE_SONY'='' -e 'DISABLE_STEAM'='' -e 'DISABLE_TESO'='' -e 'DISABLE_TWITCH'='' -e 'DISABLE_UPLAY'='' -e 'DISABLE_WARFRAME'='' -e 'DISABLE_WARGAMING'='' -e 'DISABLE_WSUS'='' -e 'DISABLE_XBOXLIVE'='' -v '/mnt/user/lancache':'/data/cache':'rw' -v '/mnt/user/appdata/lancache-bundle/log/named':'/var/log/named':'rw' -v '/mnt/user/appdata/lancache-bundle/log/nginx':'/var/log/nginx':'rw' 'josh5/lancache-bundle:latest' e56480e5e6e958ada81f2664ec12a773f44e220e1e4f3bba5e9780153256f7af /usr/bin/docker: Error response from daemon: Address already in use. The command failed. Are you using those ports on that IP already? Quote Link to comment
mrkambo Posted December 21, 2020 Share Posted December 21, 2020 (edited) Can anyone advise on how i set this up correctly using PiHole... My PiHole acts as a DHCP server and DNS - Its IP is 192.168.1.3, I've given lancache the IP of 192.168.1.4 Upstream in the container is 192.168.1.3 - is this correct? Im assuming that i give PiHole the IP for lancache as primary DNS and then leave local host as secondary DNS Any advice? Edited December 21, 2020 by mrkambo Quote Link to comment
Recommended Posts
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.