-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
get.geojs.io throws 500 for certain source ip's #48
Comments
I tested all 3 ipv6 addresses and they now seem to work. I will keep an eye on it before removing my DNS overrides (forcing v4). |
Thanks for reaching out. Unfortunately GeoJS was experiencing some issues responding to queries and it took me a bit of time to get to it. The issue should now be resolved but I need to put a long term fix in place thats proving hard to troubleshoot. |
We've also been seeing 500s as of this morning, for example: https://get.geojs.io/v1/ip/geo.json?ip=185.233.100.23 and |
It is happening consistently to me. curling https://get.geojs.io This causes geo-aware apps to break when using ipv6 :-( Let me know if you'd like me to generate some internal ip addresses with specific bytes to test from. I can do that if it would help, then again anyone could. Thank you for running this service @jloh , it helps a lot of people, and I'd like to help it help some more. It seems others are seeing the same problem: https://app.gitter.im/#/room/#jloh_geojs:gitter.im |
Hello,
Someone was complaining about a network I maintain, and said that my network is bad. However we found the application was depending on the following:
Since the 500 means that cloudflare received an error from the application I assume the application breaks for certain source ip's.
I would love to tell you the source ip/range, but I'd rather not invite an army of port scanners on that network.
I assume the 500 would be traceable in the logs.
Thank you for looking at it.
In the mean time I hope we can ask the software provider to make that request optional.
The text was updated successfully, but these errors were encountered: