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
Live listeners data not loaded #628
Comments
@bebjakub Thank you for the very detailed report. Looks like it may be an issue with our third-party IP geolocation provider, which will be a bit of a pain to resolve. I'll look into it further and update you as soon as I can. |
@bebjakub I've taken another look into this issue, and it appears the IP geolocation database service is working just fine again. There may have been a temporary outage that was responsible for the problem you experienced. If you try it again now, does it work, or does it produce the same error? |
@SlvrEagle23 Updated, but Error persists. How can I check if geolocation database service is working correctly? Anyway, I had to use manual update due old version of docker image (Docker version 1.12.2, docker-compose version 1.8.1). |
@bebjakub I've done some refactoring of the underlying code and updated the system so that IP geolocation data now comes directly from a database installed locally on the server, so no IP information has to transit out and visit a third-party API at all, and there's significantly reduced potential for problems like timeouts and such. Update again and let me know if it works any better for you. :) |
@SlvrEagle23 Thanx! Now it definitely works! :) |
Installation method
Docker
Host OS (for Docker installations)
Docker image on VC1S at Scaleway
Describe the bug
Live listeners are not loaded.
/api/station/1/listeners
has responsecURL error 28: Connection timed out after 10000 milliseconds
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Live listeners data loaded.
Screenshots
Live listeners
Desktop (please complete the following information):
Thank you! :)
The text was updated successfully, but these errors were encountered: