Hey everyone,
The migration for aqua network will happen today from 12PM- 3PM SGT
As mentioned previously, during the migration period, existing users will still have access to the network as usual, however the new user onboarding might be affected.
Please note accordingly.
Can this affect to existing users? We are having issues for logging in to our app at this moment. Is it finished?
Yes, existing users signing in with social login see this error. However existing users logging in with Metamask seems to work.
No this activity only affected new users on the aqua network.
The migration is completed. All services are functional.
ok, well as I mentioned, existing users cannot login using Social login (google) as of today. Metamask login works fine, but not social.
We are using the Aqua network still.
Any explanation for that? @yashovardhan
please open up a new thread around this with your current implementation code snippets. In the meantime we’ll investigate internally
I’m facing same issue. In my case, AWS WAF blocks new migrated web3auth service api.
It resolved after changed AWS managed rule (AWS-AWSManagedRulesAnonymousIpList) > HostingProviderIPList attributes to not blcok.
