Problem login in saphire dev

Report Outage
1

Title:

Issue

We are currently experiencing an outage affecting login with github and google providers.

Impact

This outage is affecting our login in the development environments Nevermined App and Nevermined App. In prod everything seems to work fine.

Details:

When login there is a message in the console reporting:

Error: could not retrieve nonce: Internal error, failed to get nonce with status code: 500: traceId: a646ee529f864ae08141ef27414fd258 - spanId: 9d28f1d65ad26a83

Access to fetch at 'https://node-2.dev-node.web3auth.io/sss/jrpc' from origin 'https://auth.web3auth.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. [12:05]

To reproduce you can try to login here https://testing.nevermined.app/en/ using google/github and see the error.

2

Hi Enrique! Thank you for reporting the issue you’re experiencing with logging in using GitHub and Google providers on your development environments.

Here’s a summary of the details for our support team:

  • SDK Details: Name not found
  • SDK Version: Not specified
  • Platform: Web3Auth in development environments
  • Error Message:
    • Error: could not retrieve nonce: Internal error, failed to get nonce with status code: 500: traceId: a646ee529f864ae08141ef27414fd258 - spanId: 9d28f1d65ad26a83
    • Access to fetch at 'https://node-2.dev-node.web3auth.io/sss/jrpc' from origin 'https://auth.web3auth.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
  • Impact: Unable to log in via GitHub and Google in development but works fine in production.
  • Reproduction Link: https://testing.nevermined.app/en/

Next Steps

It seems like the issue might be on our end, related to the reported outage. Please keep an eye on further updates from our team as they investigate the root cause.

If there’s anything more I can assist you with, just let me know! Your patience is greatly appreciated.

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.

3

Hi @enrique , are you still facing the issue?

4

No, it seems was solved

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.