# Dashboard graphs and charts have stopped rendering **URL:** https://community.forestadmin.com/t/dashboard-graphs-and-charts-have-stopped-rendering/4527 **Category:** Help me! **Created:** [April 22, 2022, 7:45am UTC](https://community.forestadmin.com/t/dashboard-graphs-and-charts-have-stopped-rendering/4527 "2022-04-22T07:45:40Z") **Posts on this page:** 1 **Showing post:** 6
### Author: ![anon39848301](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@anon39848301](https://community.forestadmin.com/u/anon39848301) #### Post date: [April 25, 2022, 12:14pm UTC](https://community.forestadmin.com/t/dashboard-graphs-and-charts-have-stopped-rendering/4527/6 "2022-04-25T12:14:29Z")
Well … the cloudfront HTML response may have helped here 🙂 Do you use some WAF rules on your cloudfront for security purpose? We do have a few clients referencing this issue (Request blocked) using cloudflare. This is easily checked by: - Checking your agent for the `stats` call, and check if your backend is able to send a response (At least, check if the agent is contacted) - Check the CORS request response, and check for headers, just in case the request is blocked by a CDN (X-server, or any other header) Not sure if it’s related, but looking for cloudflare, it seems like we have a few threads around this topic 🙂 > [@Cloudflare WAF blocking custom SQL](https://community.forestadmin.com/t/cloudflare-waf-blocking-custom-sql/3697): > > Expected behavior Charts that use a Custom SQL data source should not trigger basic generic security layers such as Cloudflare WAF. Sending the raw SQL as the payload seems to have this effect Actual behavior Cloudflare WAF and similar services (including Sqreen) will automatically block the request with a HTTP 403 Context We imagine Custom SQL is a popular feature and considering how widespread security tools like cloudflare are, we were wondering if there is a recommended approach to this… > [@Smart action that upload a file return 403](https://community.forestadmin.com/t/smart-action-that-upload-a-file-return-403/3354): > > Expected behavior Uploading an xml file, doing some processing, and export csv files. Actual behavior a 403 issue on that particular endpoint when clicking on the submit button to launch the post call. What is the current behavior? a 404 error over get /values (I understand this is normal from a different post here) Failure Logs Access to fetch at ‘api-to-post-the-file’ from origin ‘[https://app.forestadmin.com](https://app.forestadmin.com)’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is pr… Let me know if that helps --- _[View the full topic](https://community.forestadmin.com/t/dashboard-graphs-and-charts-have-stopped-rendering/4527)._