"unable to detect login share" error on Plug n Play

[pedro]

We’ve been encountering the following error on a Plug 'n Play verifier, affecting all our users on a specific ISP, “NET Claro”, the single largest provider in Brazil.

"Unable to detect login share from the Auth Network. This may be due to slow internet connection. Check your internet speed and try again. If you're using a vpn, please turn it off."

On the console there is some clarification on the cause of the error:

"Acess to fetch at 'https://torus-mainnet.cosmos.network/jrpc' from origin 'https://app.openlogin.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: 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."

Other similar errors crop up on the console:

This has been affecting the entire sample of users of our application using the same ISP (“NET Claro” in Brazil), leading us to think that it might be related to throtting, filtering or similar. No other services are being affected.

We’d appreciate assistance.

[vjgee]

@pedro Thanks for reporting this. Cosmos node is currently unavailable and we apologize for any inconvenience caused by the temporary shutdown of the Tendermint core node, as it may lead to some degradation on the mainnet. We are working closely with them to ensure a seamless restoration of services. You can track the progress here: Cosmos node is currently unavailable. Mainnet will see some degradation, for now, please consider other networks

In the meantime, you can make use of alternative networks.

[pedro]

Hi @vjgee ,

Some users are still continuously encountering this issue We’re at a loss of what to do in this situation; it affects a lot of users who already have created accounts.

Really appreciate any guidance.

[maharshi]

Hey @pedro,
I have reported the issue to the product team. I’ll keep you posted in case of any updates.

[pedro]

Thanks a lot, @maharshi !

[pury]

Hi everyone! I just wanted to reinforce the need for fixing this. Yesterday I would doing a live presentation of our solution and the login didn’t work. Don’t know what’s going on but we surely need to fix it. It’s a catastrophic failure since it doesn’t allow the user to access our tool.

[pedro]

Hi @maharshi,

Just checking in for any updates on this issue. Our team and users are quite anxious to have this resolved, as it’s affecting 40%+ of our userbase (the ISP in question is the largest in Brazil). Really appreciate all help on this matter.

Best

[maharshi]

Hi @pedro,
I am sorry for the inconvenience. On Friday evening for GMT5:30, a build was pushed which should have resolved some cases. The team is working on fixing the rest of the cases. Please bear with us. Thanking you for your patience.

[pedro]

Hi @maharshi ,

Thanks a lot for the update, and fingers crossed the engineers will manage to identify and fix the issue quickly. It’s really a shame that our product is targeted toward Brazilian users and so many of them are having problems

I’ve received reports today that some users are still having difficulties. I have requested screenshots and videos to check whether it’s really the same issue, but apparently it is.

I’ll keep you posted as we learn more about our users’ experiences.

[maharshi]

@pedro Hi, one more node is fixed. Could you please verify if that has fixed the issue for your users?

[circleslandnow]

Hi @maharshi! Our users also report this error from time to time. Just wanted to know if there’s anything we can do to make it more reliable (run nodes, use custom verifiers, change to a paid plan, etc.). As you can imagine OpenLogin is a very critical component in our system and we already had to cancel events because of these errors.
Sorry for just re-using this thread, but it exactly reflects our problems already

[maharshi]

Hey @circleslandnow, you can refer to this announcement here

[circleslandnow]

Hi! Thanks for the feedback. We’re currently using the @toruslabs/openlogin npm-package just like that:

    openLogin = new OpenLogin({
      clientId: Environment.openLoginClientId,
      network: "mainnet",
      uxMode: "popup"
    });
    await openLogin.init();

We’re still on version 3 and use the plug and play verifiers. So that’s going to be deprecated?
Here’s an excerpt of the issue we experienced just today:

That’s very severe for the onboarding of new users. Any advice on this is highly appreciated.

[circleslandnow]

@maharshi Btw. we just upgraded to the “scale” plan to just resolve this quickly (by the way, we’d really like to scale but that won’t happen if we cannot onboard new users

[maharshi]

@circleslandnow That’s great! For now, I’ll suggest you to start by looking at the docs. If you face any issue, feel free to start a new thread and we will be glad to help you out.