Troubleshooting 403 errors in GravityBoard
If you are seeing 403 Forbidden errors when trying to use GravityBoard, it usually means your server or hosting environment is blocking the API requests that GravityBoard needs in order to work.
What’s happening #
GravityBoard relies on the WordPress REST API to fetch and display your boards. You can check this by visiting these URLs in your browser.
Make sure to replace example.com with your site path!
https://example.com/wp-json/If that works, confirm the GravityBoard endpoint works.
https://example.com/wp-json/gravityboard/v1/And finally, confirm that the /boards/ endpoint works:
https://example.com/wp-json/gravityboard/v1/boards/If any of these return a 403 Forbidden error, it will prevent GravityBoard from functioning properly.
Likely cause #
In most cases the issue is not within GravityBoard itself. It comes from your server configuration or security firewall (such as ModSecurity, a WAF, or a host-level rule) that incorrectly blocks requests to REST API endpoints.
Note: GravityBoard itself answers with a 403 in two cases. One is an action that the board’s Permissions tab does not grant to your role. The other is a request about entry notes or attachments on a board where Entry Notes or Card Attachments is switched off. Those responses carry a GravityBoard message (You do not have permission to add attachments., Entry notes are not enabled for this board.), and a firewall block carries no such message.
How to Fix It #
Check the URLs above
Confirm whether the boards endpoint is being blocked.
Check your logs
Review your server/hosting logs around the time the error occurs. You’ll often see a firewall or security rule denying access.
Contact your hosting provider
Ask your host to adjust or whitelist the rules that are blocking REST API access to the following path, and any subpaths:
/wp-json/gravityboard/Confirm access after adjustments
After your host updates the rules, reload GravityBoard. The error should be resolved.
Next steps #
If the issue persists even after your hosting provider has made adjustments, please reach out to GravityKit support with details of your hosting environment and any firewall/security plugins you may be using.
