@denjones Thank you for the detailed response. I can see that from your example that video 1 and video 2 are coming from different urls.
Video 1 is from walkly-app.cdn.ampproject.org while video 2 is cdn-walkly-app.cdn.ampproject.org.
Are these videos stored on different CDNs i.e. is video 1 using AWS and video 2 Google CDN?
If this is the case and you are having issues with your Google Cloud CDN then I would recommend reading through the Google Cloud Storage documentation on Configuring cross-origin resource sharing. If you are still having issues with this then there is the Google Cloud Support Hub.
Indeed, the urls are coming from 2 different urls.
You have an option in the GWS settings that you can enable to cache the videos:
“Reduce hosting costs and improve user experience by serving videos from the Google cache.”
This is why there are 2 different urls: the first time the video is served from my server (AWS S3 bucket + Cloudfront), the second time when you refresh the page, the video is cached beacause of the settings and then served from the Google Cache server.
Since you have video caching turned on, it seems to me that the error you’re seeing is expected behavior.
It takes some time for the videos to be cached by the Google CDN.
When you open a web story, the story tries to load the story from the Google CDN. If it isn’t available there yet, this will cause the 500 response and the CORS message in the console. The video will be marked for inclusion on the CDN.
Once the video is available on the CDN, next time you open the story, it will load it from there as usual.
With all that said, it seems a little bit pointless to enable the Google CDN when you’ve already enabled your own.
The reason why I like the automatic Google CDN is because it creates multiple video files for 1 video and serves the best video for the user’s internet connection. But it is true what you say that it isn’t really necessary.
In the meanwhile I deleted my AWS S3 + Cloudfront setup and replaced it by another one: Wasabi (hosting) + Bunny (CDN).
Now the CORS errors are even more strange in the GWS editor. I upload for example 5 images at the same time by dragging them in the image area in the editor on the left side and only 2 out of 5 can are being displayed in the editor. The other images return a CORS error again?!?
Any idea how I can solve this?
@denjones When setting up your new CDN did you set up your new CORS headers to allow Cross-origin resource sharing as you did for your previous AWS S3 setup? If not then you will need to do this again from your Bunny CDN settings.
