Hetzner Cloud API
POST /v1/firewalls changes: CIDRs for Firewall rules not allowing host bits
Stopped workingSubscribe to Hetzner Cloud APIShare
Calls to POST /v1/firewalls on Hetzner Cloud API stopped working on December 10, 2025.
Calls it hits
POST /v1/firewalls
In Hetzner Cloud API's words
Starting on 10 December 2025, CIDRs specified as destination_ips or source_ips for Firewall rules will no longer allow for the host bits to be set.
Facts
- API
- Hetzner Cloud API
api.hetzner.cloud - Kind
- Behaviour change
- Takes effect
- December 10, 2025
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Hetzner Cloud API's own pages
Questions
When does this change take effect?
Calls to POST /v1/firewalls on Hetzner Cloud API stopped working on December 10, 2025.
What happens to calls after December 10, 2025?
They have failed since December 10, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Hetzner Cloud API 10
-
ubuntu-20.04Model retirement Stopped working -
POST /v1/firewalls/$ID/actions/set_rulesBehaviour change Stopped working -
cx52Model retirement Stopped working -
POST /v1/primary_ipsParameter removal Stopped working -
POST /v1/serversParameter removal Stopped working -
/2009-04-04/meta-dataEndpoint removal Stopped working -
/2009-04-04/user-dataEndpoint removal Stopped working -
/latest/meta-dataEndpoint removal Stopped working -
/latest/meta-data/{id}Endpoint removal Stopped working -
/latest/user-dataEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.