-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steam not always connecting #10
Comments
Additional info: The access.log of lancachenet shows nothing for that time, only entries for access before and after:
|
Are you still having this problem? Steam have recently added some built in support for caching and proper http fallback - see lancachenet/monolithic#85 - so it would be worth testing again with the latest versions of the containers. If you do still have the issue with the new version then feel free to reopen and include: What command are you using to start the containers? Do those steampowered.com hostnames correctly resolve to your lancache IP? |
I deactivated lancachenet after it gave me too many problems, specifically I noticed that I didn't get any Windows updates through it. (Yes, I know I can deactivate it.) I hadn't gotten around on trying it again and it traveled down on my to-do list.
That's nice to know! I have to give it a shot sometime again. Thanks! |
I'll raise my own issue soon, but I had a similar issue today where my daughter's PC Steam would not start up at all. Once I removed |
I set up Lancache again and the problem persists. I will try to follow @Shiroikuma 's suggestion and remove |
Okay, I still have problems with Steam not autostarting. I now also removed |
Okay, it seems to be working now and these are the URLs I have removed:
The only issue we're having here is that my wife seems to be logged out of Steam Chat repeatedly, but I cannot really link that to lancache. |
@TheSentry I had the same problem, it worked for a day and then stopped. In the end, considering Steam Natively supports lancache.steamcontent.com as a CDN if detected, I literally have removed all except for that one now. |
I recently set up lancachenet and sniproxy on my Synology NAS and so far it works fine. Or so I thought.
I noticed that Steam won't autostart anymore. The problems started after I configured my network for lancache. I attached my Steam connection_log.txt below (I replaced my SteamID with "12345"). Unfortunately, the sniproxy doesn't offer a bash, so I don't know how to look at the logs of it.
DNS redirect is done via dnsmasq on my router running Tomato.
The text was updated successfully, but these errors were encountered: