-
Notifications
You must be signed in to change notification settings - Fork 14
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
Ipwatch reporting false new ipaddress #24
Comments
Nr. 2 happens because some of the servers in serverCache.json don't exist/work anymore, and the file does not get updated regularly. I opted to disable the update mechanism in ipgetter.py and remove the invalid entries from the json myself. |
Thanks for that tip, I have edited my server list but have a question, a couple of sites have the check-human-user prompt. Do you know if this will stop IPwatch from working correctly? Also many results are in version 6 format but IPwatch only reports a version 4 number, are they converted? |
IP Watch can't handle the IPv6-only page nor the "are-you-a-human" checks. I'd welcome someone doing a once over on the server list (and adding more as appropriate). I'll happily approve a PR with updates. |
I don't know, I started to modify this but soon realized it would be faster to start from scratch.... so that's what I did. |
Here is a list of addresses that return an IPV4 result. The last 5 entries return both an IPV4 and IPV6 result but I do not know if Ipwatch can handle that? I have removed non viable addresses and added some new ones. |
After updating to Kubuntu 24.04 I experienced two new behaviour:
1/ the #23 which I have rectified and
2/ the reporting of a changed IP address when in fact it has not changed
The error is only with the external IP address. In the latest instance the queried server was ipanywhere.com.
This occurs perhaps once a week while most of the time it works correctly.
The text was updated successfully, but these errors were encountered: