Connection blocked by a firewall or IP allowlist
Problem
One of these happens with a MySQL, MariaDB, PostgreSQL, WooCommerce or API Bridge connection:
- Test Connection fails, even though the credentials are right
- The connection was created and worked, then queries started returning errors or no data
- Reports work some days and not others, with no change at your end
Why This Happens
These five connectors read from something you control: your database server, your WordPress store, your API endpoint. Every other connector reads from a platform's own public API. Two Minute Reports has to reach your server over the internet, from its own servers.
If that destination only accepts traffic from known addresses, it refuses us. The refusal usually doesn't
reach you as a clear message: a database drops the connection, a security plugin returns a generic error page,
a WAF returns 403. From inside Two Minute Reports it looks the same as a server that is down.
The intermittent version is the most confusing one, and it has one cause: an allowlist with some of our addresses on it. Requests leave from whichever of our servers is free, so a partial allowlist produces a connection that works until it happens to be handled by the address you didn't add.
Solution: Add all five addresses to the allowlist
Two Minute Reports connects from these fixed IP addresses. Add all 5 to whatever restricts access: your database firewall, security plugin, WAF or host before you create the connection. Allowing only some of them gives you a connection that works until a request leaves from one of the others.
49.13.34.182
5.75.217.220
116.203.164.91
95.216.182.151
91.99.28.86Where they go depends on the connector:
| Connector | Where to add them |
|---|---|
| MySQL | Database firewall, and the GRANT statements |
| MariaDB | Database firewall, and the GRANT statements |
| PostgreSQL | pg_hba.conf, and any cloud provider's network rules |
| WooCommerce | Security plugin, WAF, and your host's firewall |
| API Bridge | The API's own IP allowlist |
Each of those sections has the exact rules to add for that connector.
pg_hba.conf or ran GRANT is normally the provider's rules.Still Blocked?
- Check the allowlist has all five addresses, not four. A missing one produces exactly the intermittent failure described above
- For a self-hosted database, confirm the port is reachable from outside your network at all, not only from your office
- For WooCommerce, disable your security plugin briefly and run Test Connection again. If it passes, the plugin is the blocker and the addresses need to go in its allowlist
- Email [email protected] with the connector, the connection name, and what the allowlist currently contains
We can confirm from our side whether the requests are reaching your server and what it answered.
Can't Sign In With Two-Factor Authentication
Lost your phone, your authenticator code doesn't match, or your passkey or recovery code doesn't work? Fixes for signing in to the Hub with two-factor authentication.
Overview
Tips and best practices for getting the most out of Two Minute Reports with Google Sheets and Google Data Studio.