Allowlist GoDAM IPs in Cloudflare geo restrictions

GoDAM for WordPress Updated: 2026-10-29

If your site restricts traffic by country in Cloudflare, that restriction applies to GoDAM’s servers as well. Transcoding callbacks, media syncs, and REST API calls are blocked at the edge before they reach your origin, so videos stay stuck in processing and media never syncs back to your library.

GoDAM’s infrastructure runs from Germany and Finland. Allowlisting the two IP addresses below lets GoDAM through while keeping your geo restriction in place for everyone else.

You will need access to the Cloudflare dashboard for the zone, with the Firewall or Administrator role.

1. Symptoms of a geo block

  • Uploads complete, but videos stay at Transcoding and never turn ready.
  • Media appears in GoDAM Central but not in your WordPress media library, or the other way round.
  • GoDAM API calls return a 403 with a Cloudflare block page instead of JSON.
  • Cloudflare Security → Events lists blocked requests from the IPs below, with your country rule as the matched service.

2. IPs to allowlist

  • 46.4.18.78 — GoDAM Central API and transcoding callbacks.
  • 157.180.23.216 — GoDAM Central API and transcoding callbacks.
  • Both are single IPv4 hosts, so no CIDR range is needed. Allowlist both, as requests can come from either one.

Before you make any changes, check where the restriction is configured. Look in Security → WAF → Custom rules first, then Security → WAF → Tools → IP Access Rules. If the block comes from Cloudflare Zero Trust instead (Access → Applications), add the IPs to that application’s policy rather than following the steps below.

A Skip rule sits above your country block, matches the two GoDAM IPs, and stops the rules below it from running for that traffic. This is Cloudflare’s recommended approach because the exemption stays scoped to the rules you choose.

  • Open Security → WAF → Custom rules and click Create rule.
  • Name the rule so it is recognisable later, for example Skip geo block for GoDAM.
  • Switch to Edit expression and paste the expression shown below.
  • Set the action to Skip and select All remaining custom rules. Add Rate limiting rules as well if GoDAM traffic is hitting your rate limits.
  • Save the rule, then drag it to position 1, above the country block. Custom rules run top to bottom and a Block stops evaluation, so a Skip rule placed below the block never runs.
(ip.src in {46.4.18.78 157.180.23.216})

Note: Skip does not bypass every security feature. If GoDAM requests are still blocked, check which product is matching them in Security → Events and add that product to the Skip list.

4. Editing the existing geo rule

If you would rather keep a single rule, add the exception to the country rule itself. This works well on sites with only one or two custom rules, but becomes hard to read once several exceptions build up.

A rule that blocks everything outside India looks like this:

(ip.src.country ne "IN")

Add the GoDAM IPs as an exception:

(ip.src.country ne "IN" and not ip.src in {46.4.18.78 157.180.23.216})

Substitute your own country codes. If your rule allows a set of countries, the pattern is the same: append and not ip.src in {…} to the blocking condition.

Note: Older rules may use ip.geoip.country. It still works, but ip.src.country is the current field name.

5. Using IP Access rules

An IP Access rule with the Allow action is the quickest option, with no rule ordering to manage. It is also the bluntest, so read the note at the end of this section before choosing it.

  • Go to Security → WAF → Tools → IP Access Rules.
  • Enter 46.4.18.78, set the action to Allow, scope it to This website, and add a note such as GoDAM transcoder.
  • Repeat for 157.180.23.216.

Note: IP Access rules run before custom rules, and an IP-level Allow exempts that address from your custom rules, rate limiting rules, and WAF Managed Rules — not only the geo block. These matches are not recorded in Security Events either, which makes the traffic invisible when you are debugging something else later. Use the Skip rule in step 3 if you want the exemption scoped to the geo block alone.

6. Reusing the IPs across zones

If you manage several sites, store the addresses in an account-level IP list once and reference that list from each zone. Updating the list then updates every rule that points at it.

  • Go to Manage Account → Configurations → Lists and create a list of type IP named godam_ips.
  • Add both addresses as items.
  • Reference the list in the Skip rule expression on each zone.
(ip.src in $godam_ips)

7. Verifying the allowlist

  • Open Security → Events and filter by Source IP for each address. Recent entries should show Skip, or no block at all. Entries still showing Block mean the rule order is wrong or the expression does not match.
  • In WordPress, go to GoDAM → Settings and re-run the connection check, or upload a short test video and confirm it reaches Ready.
  • Allow a minute for propagation. Rule changes take effect quickly, but an in-flight transcode will not retry instantly.

8. If media is still blocked

Cloudflare is rarely the only layer between GoDAM and your site. If requests are still failing after the allowlist is in place, work through the following.

  • Zone Lockdown — if a lockdown rule restricts a path such as /wp-json/, the GoDAM IPs must be listed there too. Skip and Allow do not cover it.
  • Origin firewall — ufw, firewalld, CSF, or a cloud security group can block the same traffic independently of Cloudflare. Allow both IPs on ports 80 and 443.
  • Security plugins — Wordfence, Solid Security, and similar plugins maintain their own country blocking. Add the IPs to the plugin’s allowlist as well.
  • Bot protection — Super Bot Fight Mode can challenge server-to-server requests. Include Super Bot Fight Mode in the Skip rule to resolve this.
  • REST API availability — GoDAM communicates with your site over the WordPress REST API. If /wp-json/ is disabled or rewritten, allowlisting the IPs will not help on its own.
  • Proxy in front of Cloudflare — if another proxy or load balancer sits ahead of Cloudflare, the source IP reaching the edge may differ. Confirm the value in Security Events rather than assuming.

If you face any issues, please reach out to our support with the Ray ID of a blocked request.