EDIT: I thought it had to do with Javascript misbehaving again (I’m not using any caching plugins), but was unfortunately conincidence 🙁 Even with the Javascript option disabled, visits get registered with 127.255.255.0.
Starting from version 3.4.3, local IP addresses won’t be masked anymore.
Care to elaborate?
I highly doubt that e.g. these recent ones are accesses from localhost:
179.199.134.XXX - 179-199-134-XXX.user.veloxzone.com.br - [01/Dec/2013:19:10:29 +0000] "GET /archives/1307 HTTP/1.0" 200 43042 "https://www.google.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.0.0 Safari/537.36"
207.34.115.XXX - - [01/Dec/2013:20:37:03 +0000] "GET / HTTP/1.0" 200 16717 "http://www.[…]" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)"
149.119.218.XXX - - [01/Dec/2013:21:20:39 +0000] "GET /alphabet HTTP/1.0" 200 44591 "https://www.google.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36"
178.167.148.XXX - 178.167.148.XXX.threembb.ie - [02/Dec/2013:00:40:50 +0000] "GET /archives/3568 HTTP/1.0" 200 18260 "http://www.google.ie/[…]" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)"
Yet they’re all logged in my database as coming from 127.255.255.0 and no country.
Can you send me the unmasked IP Addresses through our contact form? I would like to run some tests…
OK, did so.
For what it’s worth, I upgraded to SlimStat 3.4.3 today, and the problem persists.
(Of course, I meant 3.4.2 in my original posting; I confused it with the current WordPress version number)
Is your web server behind a firewall/proxy? Are you using our Firewall Fix add-on?
How can I test whether I’m behind a firewall? My host writes in their FAQ that they use firewalls, however, that doesn’t seem to have been a problem previously.
I will reinstall Slimstat 3.4.1, which worked when I used it, to see if that also makes problems. I’ll probably report back only tomorrow since I (actually) don’t seem to get many visitors today.
EDIT: gethostbyaddr() at least seems to work with all the IPs I reported to you as having registered wrongly with Slimstat. I suppose this would be a thing that possibly wouldn’t work if I were behind a (very strict) firewall?
Carbeck,
it’s a slightly different issue. gethostbyaddr() already has the IP address. The problem is HOW that IP address is being given to SlimStat for processing. If the firewall doesn’t send the right headers to the webserver, that could be the issue.
Slimstat 3.4.1 seems to still work fine. *scratches head*
Yes, we changed a setting related to local IP addresses in version 3.4.2. But I need to run some more tests to see how that is affecting your pageviews. Could you send me a list of IP addresses that got converted?
I’ve just sent you a bunch of IPs that Slimstat 3.4.3 logged correctly via the contact form.
Hm, I would need those that were NOT logged correctly, when the privacy setting is enabled.
Oh sorry, I misunderstood you then. Sent you those that didn’t work again.
The issue is related to your server running on a 32-bit operating system, which triggers the integer upper limit in PHP, when numbers are bigger than that. I sent you a snippet of code to test, see if that fixes it so that I can add it to the next release.
