# \[Archive\] CORS Support Needed for Dev-Node Endpoints (https://node-x.dev-node.web3auth.io/sss/jrpc) **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Created:** [July 11, 2025, 8:58am UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991 "2025-07-11T08:58:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kieuanh.hcmut](https://avatars.discourse-cdn.com/v4/letter/k/b487fb/32.png) [@kieuanh.hcmut](https://builder.metamask.io/u/kieuanh.hcmut)\ **Post date:** [July 11, 2025, 8:58am UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991/1 "2025-07-11T08:58:42Z")
> **🏛 Archived Content from Web3Auth Community** > > This topic was originally posted by **kieuanh.hcmut** on 7/11/2025. > This content has been migrated from our previous community forum to preserve valuable discussions. * * * Hello Web3Auth Support Team, We are integrating Web3Auth into our browser-based wallet application (With MPC TSS - sapphire\_devnet ), and have encountered a CORS issue with your dev-node endpoints while loginWithJwt (testing in iOS platform) Detail: - Our app makes requests from a browser/webview context (origin: chrome://wallet). - Requests to your main API endpoint (e.g., [https://api.web3auth.io/signer-service/api/allow](https://api.web3auth.io/signer-service/api/allow)) succeed, as these endpoints return the appropriate CORS headers: Access-Control-Allow-Origin: chrome://wallet Access-Control-Allow-Credentials: true - However, requests to the dev-node endpoints (e.g., [https://node-1.dev-node.web3auth.io/sss/jrpc](https://node-1.dev-node.web3auth.io/sss/jrpc), [https://node-2.dev-node.web3auth.io/sss/jrpc](https://node-2.dev-node.web3auth.io/sss/jrpc), etc.) fail due to missing CORS headers. The browser blocks these requests with the following error: “Fetch API cannot load [https://node-x.dev-node.web3auth.io/sss/jrpc](https://node-x.dev-node.web3auth.io/sss/jrpc) due to access control checks.” - The network response for these endpoints does not include any Access-Control-Allow-Origin header. Request: Could you please update the CORS configuration for the dev-node endpoints to include the following headers in responses to browser-based clients? Access-Control-Allow-Origin: chrome://wallet Access-Control-Allow-Credentials: true Or, for development purposes, you could use: Access-Control-Allow-Origin: \* This change will allow browser-based applications to interact with your dev-node endpoints without being blocked by CORS policy. Thank you for your help! Best regard, Anh ---
**Author:** ![w3abot](https://avatars.discourse-cdn.com/v4/letter/w/4da419/32.png) [@w3abot](https://builder.metamask.io/u/w3abot)\ **Post date:** [July 11, 2025, 9:00am UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991/2 "2025-07-11T09:00:36Z")
Thank you for the detailed report, Anh! **Summary of Your Issue:** - **Integration Context:** Browser-based wallet app using Web3Auth with MPC TSS (sapphire\_devnet), custom JWT login. - **Problem:** CORS errors when your app (origin: `chrome://wallet`) tries to access dev-node endpoints like `https://node-x.dev-node.web3auth.io/sss/jrpc`. These endpoints do not return `Access-Control-Allow-Origin` headers, causing browser requests to fail. - **Working:** Main API endpoints (e.g., `https://api.web3auth.io/signer-service/api/allow`) do return the correct CORS headers and work as expected. - **Request:** Update CORS configuration on dev-node endpoints to allow requests from your app’s origin (or use `*` for development). * * * ### Details for Support Team - **Platform:** Browser/Webview (`chrome://wallet`) - **SDK:** Not specified, but using MPC TSS (sapphire\_devnet) and custom JWT login flow. - **Endpoints affected:** All `https://node-x.dev-node.web3auth.io/sss/jrpc` endpoints. - **Endpoints working:** `https://api.web3auth.io/signer-service/api/allow` - **Custom Auth:** Yes, using custom JWT. - **Request:** Add CORS headers (`Access-Control-Allow-Origin: chrome://wallet` and `Access-Control-Allow-Credentials: true`) to dev-node endpoints. * * * ### Next Steps / Recommendations - This is a **backend configuration/feature request** for the dev-node environment. No further code or JWT details are needed from your side right now. - If you need a workaround while waiting for the CORS update, you could consider using a backend proxy server in your development setup, but for production and best security, native CORS support is ideal. **Reference Docs:** - [Web3Auth Custom JWT Guide](https://web3auth.io/docs/authentication/custom-connections/custom-jwt) - [CORS in Web3Auth Telegram Mini App Example](https://web3auth.io/docs/guides/telegram-miniapp-server#part-2-cors-configuration) * * * **Support Team:** Please review and consider updating the CORS policy for dev-node endpoints as per the above request. This will enable browser-based integrations using custom JWT auth to function correctly in development environments. Anh, we’ll keep you updated here as soon as there’s progress or a fix! If you have further technical details or encounter new errors, feel free to share them. Thank you for helping us improve the developer experience! > Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible. > Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. [Web3Auth Developer Office Hours](https://web3auth.io/community/t/web3auth-developer-office-hours/8777) ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [July 21, 2025, 4:47am UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991/3 "2025-07-21T04:47:54Z")
It might be an intermittent issue on `sapphire_devnet`. Can you please try again and confirm if this issue still there? ---
**Author:** ![kieuanh.hcmut](https://avatars.discourse-cdn.com/v4/letter/k/b487fb/32.png) [@kieuanh.hcmut](https://builder.metamask.io/u/kieuanh.hcmut)\ **Post date:** [July 21, 2025, 4:50am UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991/4 "2025-07-21T04:50:27Z")
Hi Maharshi, I tried it and the issue is still there [![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/ff6ab88fd52dde0af02343994dd6879f786c1063.jpeg) image1920Ă—1002 169 KB ](https://web3auth.io/community/uploads/default/original/2X/7/7e8f03181bea35dd040cd694d1dfb8e20f12d40e.jpeg "image") ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [July 30, 2025, 12:44pm UTC](https://builder.metamask.io/t/archive-cors-support-needed-for-dev-node-endpoints-https-node-x-dev-node-web3auth-io-sss-jrpc/991/5 "2025-07-30T12:44:44Z")
Hey @kieuanh.hcmut Can you please join tomorrow’s Office Hours? We would be able to give you the dedicated attention this issue needs. ![](https://web3auth.io/community/letter_avatar_proxy/v4/letter/m/ce7236/48.png)[Web3Auth Developer Office Hours](https://web3auth.io/community/t/web3auth-developer-office-hours/8777) [Announcements](https://builder.metamask.io/community/c/announcements/5) > Stuck somewhere in the integration? Join the biweekly MetaMask Office Hours & get help from our team. > > Before following the below steps, make sure your discord username is not a generic one (anything of the format name\_{any 6 digits}). If it is, follow these steps to change your username: [https://support.discord.com/hc/en-us/articles/213480948-How-do-I-change-my-Username](https://support.discord.com/hc/en-us/articles/213480948-How-do-I-change-my-Username) > The above step is mandatory to if you username is a generic one. > First and Third Thursday every month, 10:00 AM EST > Make sur…