uklans/cache-domains

"http://diagnostics.lancache.net/" Shows 0/26 providers are working

Jimbo7136 opened this issue · 6 comments

I have only tried steam and have not verified the other 25 providers but it would seem either the diagnostics tool is broken or something is very wrong with lancache itself.

Lancache bundle application on Unraid 6.9.2

Not using sniproxy

DNS Configuration

All handled by lancache bundle app

Sniproxy output

Please paste the output from docker logs <sniproxy container name/id> | sed 's/.*\:443 \[//;s/\].*//' | sort | uniq -c below

<!-- If you are running sniproxy paste the output to the following command
docker logs <sniproxy container name/id> | sed 's/.*\:443 \[//;s/\].*//' | sort | uniq -c
-->

I have the same issue. Tried from 2 machines connected via lancache server to the internet.
output of "docker exec -it lancache tail -f /data/logs/access.log | ccze -A" shows that lancache itself is working fine.
At least apart from rockstar, which currently seems not to work for me.

Seeing the same results with all but Steam enabled.

The diagnostics tool covers alot of things and isn't always a great test. The best way to try to see it workinng is in an private browsing mode. However its more reliable to nslookup one of the domains from a client.

Seeing the same even though an nslookup shows that providers are resolving to local lancache instances.

Chrome Browser fails and Firefox works as intended. It seems to be a security thing with Chrome (watching you and keeping you safe) ;)

Same result in firefox.