App for Cloudflare® Pro 1.9.9

[moldypenguins]

I added my API token with the proper permissions and I get the following errors.

Page: /wp-admin/options-general.php?page=app-for-cf

Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 1125
Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 1125
Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 1138
Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 1138
Warning: Undefined array key "browser_cache_ttl" in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 825
Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Repository\Cloudflare.php on line 825
Warning: Trying to access array offset on null in .\wp-content\plugins\app-for-cf\src\DigitalPoint\Cloudflare\Admin\Template\Settings.php on line 716

 

[moldypenguins]

Fixed it. I had to add my own ip address to the Client IP Address Filtering section as I am running locally.

 

[Shawn]

Oh ya… if you are filtering API usage by IP address, it tends to cause problems. If you use presigned URLs it causes even more problems because it’s the end user viewing the presigned URL that’s having its IP blocked.

The API token is scoped for the absolute minimum it needs, so maybe instead of IP whitelisting, you could restrict it to just that specific zone. Although, if you are in a situation where users on different IPs are getting your API token, it might make sense to figure out how.

TL;DR: IP restrictions tend to cause problems… presigned URLs won’t work, hosting company changing your server IP and things break, etc.