Some of image cdn links from prismic gave 403 error

Many of the image url's from prismic have given 403 errors until the cache is cleared. We usually cache the api response and use it. So until the cache got cleared the images were being shown 403 error. But after that the images worked but with new cdn link. This is same as what we saw on Prismic official website also yesterday. The below images are just to show same thing happened to our website since we forgot to take screenshots before clearing cache which made it work again



Does any one know reason for this?
My guess is they changed CDN servers so which caused issue. but i am not sure entirely

Hi @sreeram.a ,

Are you blocking any URLs or using a proxy that might be?

Prismic images are delivered through imgix servers.

Are you seeing this is every browser you use? It might be a plugin interfering.

No I am not using any plugins. and there are 3 users using it, we are in $30/month plan. and all of got the issue at same time. we each were publishing a document. Sudenly we got error that we cant save our documents and then suddenly when we cleared our cache and some opened in incognito and then for all of us we are routed to onboarding link and i again clicked get started and all steps thinkingg we will get back but our dashboard is empty and no documents and custom types are there but our media fiiles are intact and API calls are working

Hi @sreeram.a,

We had an issue yesterday that briefly impacted repositories. Because it made it appear as if the repository was empty, you were faced with the onboarding guide that asks you to select a master locale. As you mentioned, if you clicked through, you might have changed your master locale. This could cause your documents to not render properly/your API to not return what it should, as your document are set under a specific master locale and won’t “respond” to a different one.

We checked the logs to see a list of repositories that had their master locales changed, if you let me know yours I can double check it was one of the ones affected but I think that is the case. You need to revert your master locale back to what it used to be, and it should fix it!

Let me know if anything needs clarifying :slight_smile: