Last tested: May 1, 2020
We had issues contacting the CDN. Page speed may be impacted
This issue likely originates from the user's computer or the network that the computer is on. However, it's worth checking using the
curl command below to ensure that Looker's CDN is working normally for your host.
- If you are on Chrome, try in incognito. If the error goes away:
- Clear cache
- Or perform a hard reset first, as this may be less intrusive (Command - Shift - R on Mac, Ctrl - F5 on Windows)
- Disable adblock
- Clear cache
- Check if we can reach the CDN for your instance by running this in your terminal:
curl -I -s -X GET -H "Origin: https://INSTANCE_NAME.looker.com" https://static-b.lookercdn.com/4.12.7/webpack/vendor.webpack-a97be941.js
HTTP/1.1 200 OKis the expected response
- Are all users affected?
- Bigger issue, possibly cause by firewall, proxy or ad block
- This problem can also likely be remedied by enabling the browser service-worker cache, even if the customer is unable to make changes to their local network to reach the CDN.
Can't I just disable the CDN?
Although you can disable the CDN in the Admin - General settings, it's definitely not ideal to turn off the CDN in almost any situation. Any user that is not within your network and physically close to the server will probably have a slower experience without the CDN. Even people on the same network could have a slower experience due to browser limitations.