Troubleshooting URL and CORS configuration errors

What we'll cover

Troubleshooting assets that cannot be loaded due to URL and/or CORS configuration errors. 

• Troubleshooting URL errors
• Troubleshooting CORS errors
• Why is CORS required?

Troubleshooting URL errors

1. Check that the asset's URL is correct and is externally available.
2. Enter the assets URL into your browser to verify that the video will play in your browser.
3. If the asset does play successfully you should be able to use the video in Alegion Control. If you continue experiencing difficulties please refer to Asset Troubleshooting Steps or contact Alegion Support. 

Troubleshooting CORS errors

1. Check that the bucket or server where the assets are hosted is correctly configured to allow cross-origin requests. The cross-origin resource sharing (CORS) policy should be configured as follows (this sample is from Amazon S3, but equivalent configurations are available in other hosting platforms): 

   [
     {
       "AllowedHeaders": [
         "*"
       ],
       "AllowedMethods": [
         "GET"
       ],
       "AllowedOrigins": [
         "https://portal.alegion.com"
       ],
       "ExposeHeaders": []
     },
     {
       "AllowedHeaders": [
         "*"
       ],
       "AllowedMethods": [
         "GET"
       ],
       "AllowedOrigins": [
         "https://work.alegion.com"
       ],
       "ExposeHeaders": []
     }
   ]

   
   
2. If you continue experiencing difficulties please contact Alegion Support.

Why is CORS required?

Alegion's web-based user interfaces load images, videos, and some text snippets asynchronously for various reasons, including the benefits of streaming video. This pattern is commonplace across modern web applications. For security reasons (such as to prevent a man-in-the-middle attack), browsers enforce the Cross-Origin Resource Sharing mechanism for all asynchronous requests.