-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
Blocking 20.60.20.4 stops some Steam games from cloud saving #503
Comments
Can confirm this behavior for Simplewall using default spy-blocking rules. With 20.60.20.4 blocked, the user can't use Steam Cloud features, e.g. uploading screenshots, sending media in chat etc. Those are the errors so other people can find this issue and identify the problem: |
On Windows 10 19041, Steam 1689034492 (Beta) from Scoop and WindowsSpyBlocker from Scoop, I can normally upload screenshots via Screenshot Manager. |
Checked it right now, still can't upload screenshots or send media in chat with 20.60.20.4 blocked. Cloud sync seems to be working tho. |
Behaviour
Steps to reproduce this issue
Expected behaviour
Games should cloud save as normal.
Actual behaviour
Steam gets stuck in a "cloud sync" error.
Rules used
I applied the blocklist through WPD, not exactly sure how it's done with this program.
Configuration
United-States
Windows 10
I just figured it would be important to note here. This really had me so confused for a while, I talked to Steam support assuming it was an error on their end. The cloud.log file that Steam generates simply said "failed to download/upload," without any further information. I ended up using Windows' built-in firewall logging and found out that the failed traffic was from 20.60.20.4, which I realized was one of the IP's blocked. Again, I use WPD, so I apologize if I'm not as familiar with this specific project (though I know this is the one that WPD and many others are based on). I just figured I'd mention it, as Steam is pretty popular and other people with the same issue as me might not immediately realize it's an IP blocking issue with this program (and other subsidiaries), as opposed to a Steam/Steam Cloud issue.
The text was updated successfully, but these errors were encountered: