Allowing GravityKit license checks through your firewall
If your server is behind a strict firewall or WAF that blocks outbound connections, your license activation, validation, or plugin update requests to GravityKit can be blocked. This article covers what to allow so those requests can go through.
What to allow #
Your WordPress site makes outbound HTTPS requests to our licensing and distribution endpoints. To allow them, permit outbound traffic on port 443 (HTTPS) to the following hosts:
store.gravitykit.comwww.gravitykit.com
Domain-based allowlisting is the recommended approach. Our endpoints sit behind Cloudflare, which rotates IP addresses without notice, so a specific IP you allow today may not be correct tomorrow.
If your firewall only supports IP addresses #
If your firewall, WAF, or hosting control panel can’t allow by domain, use the published Cloudflare IP ranges instead of a single IP:
Cloudflare publishes both IPv4 and IPv6 ranges. Allowing outbound traffic to those ranges on port 443 covers our endpoints without needing to track individual IP changes.
If your server’s own IP is being blocked on our side #
Occasionally our own WAF (also Cloudflare) flags requests from certain datacenter or shared IPs and blocks them. If you’ve allowed outbound traffic on your side and license activation still fails, this may be the cause.
In that case, share your server’s public IP address with our support team and we’ll add it to our allowlist. See How to share your IP address with support for the fastest way to find and send it.
Which direction does the traffic go? #
License checks are outbound requests from your WordPress site to our hosts. Many WAFs only filter inbound traffic to a server, so if the WAF isn’t the cause, the block may be coming from a separate outbound firewall rule, a hosting provider’s egress filter, or our own WAF as described above. Reviewing your firewall logs for blocked outbound requests to store.gravitykit.com, www.gravitykit.com, or the Cloudflare IP ranges is the fastest way to pinpoint where the block is happening.