Why ghostery try to connect to 10.0.4.162 or 10.0.5.141 ? #199
Comments
|
This issue should be fixed now. Please let us know if you are still seeing those network calls. There was a bad header redirect on https://ghostery-sign.ghostery.com/config, which is part of our proxy network. We use this for our Human Web and Anti-Tracking features. We deployed an update to our backend last week to clean it up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
With extension v8.2.4, I noticed today that it try to connect to 10.0.4.162 or 10.0.5.141, why ?
If this extension is disabled in my browser, there is no request to previous IPs anymore, so it seems to be triggered by ghostery !?
Expected Behavior
No request to internal network addresses.
Actual Behavior
TCP request sent to previous IPs.
Steps to Reproduce
Versions
The text was updated successfully, but these errors were encountered: