geoIP blocking tickets from private IPs

Technical assistance
1

Infos:

  • Used Zammad version: 7.2.0-154eb34c.docker
  • Used Zammad installation type: docker-compose
  • Operating system:
  • Browser + version:

Expected behavior:

Creation of ticket via webhook

Actual behavior:

422

ERROR – : https://geo.zammad.com/lookup?ip=10.2.3.4: #<RuntimeError: 422/Faulty IP address>

Steps to reproduce the behavior:

If got a service (zabbix) running and creating tickets via webhooks on a separate user with its token.
It has been doing that for like years.
Today I’ve come to find that the last ticket is 5 days old even though it usually sends 10 per workday.
Its logs say 422 and zammad says:

ERROR – : https://geo.zammad.com/lookup?ip=10.2.3.4: #<RuntimeError: 422/Faulty IP address>

I don’t know If earlier geo.zammad.com had accepted private adresses or if earlier zammad didn’t call that service.
My reverse proxy is still working fine.

I can see that https://geo.zammad.com/lookup?ip=10.2.3.4 fails while e.g. https://geo.zammad.com/lookup?ip=23.88.61.115 succeds

2

@mgruner that doesn’t seem right. Back in my days ™ I believe private IPs just returned 200 and an empty array. A private IP technically is not a faulty IP address - so even the return code is… difficult.

Even if, Zammad should then not log errors, if it’s an expected behavior in terms of geo.zammad.com.

3

@bobb We did have some security related changes in geo.zammad.com. But it’s not geo that is blocking the creation of tickets, it’s a behaviour in Zammad (if I understood your report correctly). So could you please open an issue at Issues · zammad/zammad · GitHub so that the team can track this and analyze the situation?

4

thank you.
I raised it in geoIP is blocking tickets from private IPs · Issue #6415 · zammad/zammad · GitHub and added your comments

6

Well looks like a fails alarm - sorry
a colleague renamed some groups and didn’t update that change in the respective settings

The geo .zammad .com error was a red herring apparently