# \[Archive\] CORS policy issue during web3auth modal initialization

**URL:** <https://builder.metamask.io/t/archive-cors-policy-issue-during-web3auth-modal-initialization/2243>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [December 22, 2022, 9:48am UTC](https://builder.metamask.io/t/archive-cors-policy-issue-during-web3auth-modal-initialization/2243 "2022-12-22T09:48:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [December 22, 2022, 9:48am UTC](https://builder.metamask.io/t/archive-cors-policy-issue-during-web3auth-modal-initialization/2243/1 "2022-12-22T09:48:53Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **githubdiscussions** on 12/22/2022.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Hi everyone  
I am currently trying to implement the modal version of web3auth on a cross-origin-isolated website. During the initialization of the interface, the component called "sdk-modal" fails to download due to a lack of cross-origin-resource-policy in the header. Is there any way around that issue?

  
   
 Originally posted by: [Myrindd](https://github.com/Myrindd)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/1119](https://github.com/orgs/Web3Auth/discussions/1119)