Skip to content
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

Why ghostery try to connect to 10.0.4.162 or 10.0.5.141 ? #199

Closed
ContribOpenSource opened this issue Oct 1, 2018 · 1 comment
Closed

Why ghostery try to connect to 10.0.4.162 or 10.0.5.141 ? #199

ContribOpenSource opened this issue Oct 1, 2018 · 1 comment

Comments

@ContribOpenSource
Copy link

@ContribOpenSource ContribOpenSource commented Oct 1, 2018

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

  1. launch browser
  2. wait 2 minutes
  3. look at network traffic

Versions

  • Browser: chromium 65
@christophertino
Copy link
Member

@christophertino christophertino commented Oct 17, 2018

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
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants