-
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
Mapping no longer works? #21
Comments
Hi, are you currently using v2.3.0? You can fix it in 2 ways:
|
@kmanwar89 Maybe you should secure your n8n application (auto.domain.com). It's useable without authentication. NPM can help you there. |
Thanks for calling that out - I hadn't gotten around to security it (usually put it behind Authentik). I do use NPM so I'll look into implementing the ACL's, but the high requests towards that domain are because I have a Webhook trigger which seems to be polling a few times a minute. Your #1 fix you posted above was super simple to do, and now mapping has returned to working as expected. Thanks for the help! |
No problem. Security is important. Glad to hear. Enjoy :) |
Hi there,
Installed npmgrafstats and love it, but something seems to have broken the mapping functionality and I can't seem to find any indication as to what/why/how.
I installed it on 7 JUN when I raised #14 . It's been running since, and I suspect my WAN IP changed at some point, because I observed the logs stopped parsing on or about 19 JUN. I fixed the WAN IP (before pulling the new version of the image where you addressed #15 ) and saw it began parsing again, but the mapping functionality is lost.
The below screenshot shows logs are accurately being parsed, but the mapping function is not functioning (2nd screenshot)
Snippet of docker compose logs (below) show the lat/long is being properly identified as well, but I'm happy to share over any relevant logs or output needed. I'm currently using the latest GeoLite2-City.mmdb file which was recent as of 7 JUN, but can upgrade to a more recent one if needed, thanks!
The text was updated successfully, but these errors were encountered: