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

Jump to bottom

Same IP (server host ip) for all visitors when using tracker-proxy #11447

Closed
EdgarPE opened this issue Mar 2, 2017 · 4 comments
Closed

Same IP (server host ip) for all visitors when using tracker-proxy #11447

EdgarPE opened this issue Mar 2, 2017 · 4 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@EdgarPE
Copy link

EdgarPE commented Mar 2, 2017 •
edited

For some websites I am using piwik tracker proxy (https://github.com/piwik/tracker-proxy), but in Visitors in Real Time widget every user has the same IP address, the address of the web server IP. There are no other proxy-s involved.

The tracker proxy does a request to real piwik tracker like this one:
91.X.Y.Z - - [02/Mar/2017:16:55:57 +0100] "GET /piwik.php?cip=212.A.B.C&token_auth=9c43c...

91.X.Y.Z is the server IP, 212.A.B.C is clients real IP address.

So the tracker proxy sets the cip query parameter right, the correct IP is there. Still, the real piwik server do not obey to this, but uses the server host IP address.

If you need any more info let me know.
@EdgarPE
Copy link
Author

EdgarPE commented Mar 2, 2017

Some more info: Piwik version: 3.0.2 (upgraded from 2.x)

There are sites on different web servers with tracker proxy involved. All the stats of these sites shows the actual web server IP of that site as client IP. There is one site, which do not use tracker proxy, it uses the embeddable JS connecting directly to piwik server. The client IP-s are correct on that site.

@tsteur
Copy link
Member

tsteur commented Mar 2, 2017

Can you check that the configured token auth is correct?

@EdgarPE
Copy link
Author

EdgarPE commented Mar 2, 2017

Oh, the AUTH_TOKEN was not matching. The 2.x -> 3.x upgrade must have changed it. Thanks! And also thank you for this awesome piece of software!

@EdgarPE EdgarPE closed this as completed Mar 2, 2017
@tsteur
Copy link
Member

tsteur commented Mar 2, 2017

You're welcome. Glad it works 👍

@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @EdgarPE