Open CharbelRGC opened 6 years ago
every 2 month, i have to stop nginx, unbound, delete riot cache content folder, restart unbound, nginx and it works again....
Le dim. 5 août 2018 à 05:59, Charbel Issa notifications@github.com a écrit :
Been Using this cache for quite a while , only recently i started having problems with Riot Games. Basically whenever any of my clients DNS is set to fetch data from the cache server , everything works expect for Riot ( Steam and everything else are working normaly) . Basically what happens is that Riot Games would start , give an error that it has to go back with the version and then try to update itself again , i click okay it restarts and gives the same error again . ( I've had this problem for almost 2 weeks at more than 1 center ) . Any help would be appreciated Thank you
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bntjah/lancache/issues/108, or mute the thread https://github.com/notifications/unsubscribe-auth/ASWSQD73kwLw03KqpJxY8P2-bwS_chXLks5uNlF2gaJpZM4VvNEA .
I've never had to do that before , still i did it the same problem is still happening .Its weird that no1 else is having this problem (i think ?doesn't seem to be any reports on it )
is your unbound up to date along with the lancahe-riot.conf?
server { listen lancache-riot deferred default; servername riot ; access_log /srv/lancache/logs/Access/riot.log main buffer=128k flush=1m; access_log /srv/lancache/logs/Keys/riot.log keys_range buffer=128k flush=1m; error_log /srv/lancache/logs/Errors/riot.log;
# Default Node
include lancache/resolver;
include lancache/cache-key-default;
location ~ ^.+(releaselisting_.*|.version$) { proxy_pass http://$host; }
location / {
# Some downloads are very large so we cache based on
# range to keep single downloads quick and hence ensure
# interactivity is good.
proxy_bind 10.0.4.20;
#testing cache of 200 value
#proxy_cache_valid 200 90d; proxy_cache_valid 206 90d;
proxy_cache riot;
proxy_read_timeout 150;
include lancache/proxy-cache;
include lancache/cache-range;
}
}
Havent really updated that in a long long while , that should be it Thank you !
Been Using this cache for quite a while , only recently i started having problems with Riot Games. Basically whenever any of my clients DNS is set to fetch data from the cache server , everything works expect for Riot ( Steam and everything else are working normaly) . Basically what happens is that Riot Games would start , give an error that it has to go back with the version and then try to update itself again , i click okay it restarts and gives the same error again . ( I've had this problem for almost 2 weeks at more than 1 center ) . Any help would be appreciated Thank you