-
Notifications
You must be signed in to change notification settings - Fork 29
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
GOG Galaxy (Windows) #456
Comments
Hello! @DandelionSprout I just test the GOG client and can confirm that after adding an app to the filtering list it faced connection issues. |
Checked on Windows 10. |
The "Default filtered apps" list on Windows is very small, and only counts perhaps 12 web browsers and the Microsoft Store UWP apps. So if we only were to make exclusions for those default apps, the HTTPS exclusion list would be pretty small too. 😅 |
After spending a week looking into why GOG Galaxy was unable to connect online while AdGuard for Windows was turned on and with GOG Galaxy as a filtered application, it seems that GOG Galaxy doesn't seem able to use AdGuard's TLS certificate, making an HTTPS exclusion necessary.
After a few days, I seem to have ruled out
$removeparam
entries as having caused it.But this is where it gets tricky, because this is the kind of scenario where an entire .exe would've needed to be excluded on Windows, and not just request-domains.
Excluding
cfg.gog.com
makes it possible to log in, but in order to remove "Sorry, we couldn't load the data" error messages afterwards, quite a lot more exclusions seem to be needed:AdGuard version: AdGuard for Windows 7.8
Filterlists in use: None during today's testing session
GOG Galaxy version: 2.0.45.61 (Seems to apply to 2.0.37.384 as well)
The text was updated successfully, but these errors were encountered: