# geoIP blocking tickets from private IPs

**URL:** https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289
**Category:** Technical assistance
**Created:** [September 29, 2026, 3:32pm UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289 "2026-09-29T15:32:38Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![bobb](https://community.zammad.org/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bobb](https://community.zammad.org/u/bobb)
#### Post date: [September 29, 2026, 3:32pm UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/1 "2026-09-29T15:32:38Z")

</div>

### 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:](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:](https://geo.zammad.com/lookup?ip=10.2.3.4:) #\<RuntimeError: 422/Faulty IP address\>

I don’t know If earlier [geo.zammad.com](http://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](https://geo.zammad.com/lookup?ip=10.2.3.4) fails while e.g. [https://geo.zammad.com/lookup?ip=23.88.61.115](https://geo.zammad.com/lookup?ip=23.88.61.115) succeds

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [September 29, 2026, 8:07pm UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/2 "2026-09-29T20:07:18Z")

</div>

@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](http://geo.zammad.com).

---

<div class="post-metadata">

### Author: ![mgruner](https://community.zammad.org/user_avatar/community.zammad.org/mgruner/32/5334_2.png) [@mgruner](https://community.zammad.org/u/mgruner)
#### Post date: [September 30, 2026, 5:27am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/3 "2026-09-30T05:27:59Z")

</div>

@bobb We did have some security related changes in [geo.zammad.com](http://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](https://github.com/zammad/zammad/issues) so that the team can track this and analyze the situation?

---

<div class="post-metadata">

### Author: ![bobb](https://community.zammad.org/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bobb](https://community.zammad.org/u/bobb)
#### Post date: [October 1, 2026, 8:37am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/4 "2026-10-01T08:37:20Z")

</div>

thank you.  
I raised it in [geoIP is blocking tickets from private IPs · Issue #6415 · zammad/zammad · GitHub](https://github.com/zammad/zammad/issues/6415) and added your comments

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [October 1, 2026, 10:34am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/5 "2026-10-01T10:34:52Z")

</div>



---

<div class="post-metadata">

### Author: ![bobb](https://community.zammad.org/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bobb](https://community.zammad.org/u/bobb)
#### Post date: [October 1, 2026, 10:59am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/6 "2026-10-01T10:59:03Z")

</div>

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

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [October 1, 2026, 10:59am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/7 "2026-10-01T10:59:24Z")

</div>



---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [October 8, 2026, 10:59am UTC](https://community.zammad.org/t/geoip-blocking-tickets-from-private-ips/21289/8 "2026-10-08T10:59:25Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
