Hey @georgeschouchani1, I hope you have ensured that the given clientId is on mainnet and has the domain(https://login.eumlet.com) whitelisted. Because currently, there are no ongoing issues with client whitelisting. Please verify if you are passing the same client ID in your application for which you have whitelisted the domain.
We ensured that the ClientID is whitelisted, we also tried on another ClientID for another mainnet as well and is still does not work. There is something broken, and the error is being shown from the openlogin side
Can you check if there is an issue from Web3Auth side? Its very weird our dashboard 100% ensures that this is available.
I think it is important to node that on localhost where whitelist does not occur, it works perfectly.
Please whitelist the domain on which you are hosting, I am inclined to believe that you have somehow missed that step. I’ll link relevant doc here.
We have whitelisted all domains, subdomains as well as the website we are hosting on and it is still not working. We made sure to try to remove them and add them again and still the same response. I don’t actually think this is the issue. It was working fine 1 week ago, and now its broken when we updated to latest version
Any update on this front?
Hello? is there any update here? It has been lingering for a while? Is it possible to schedule a call with the team to solve this?
Hello was there a solution found, it has been 2 weeks now without any response.
@georgeschouchani1 We have been noticing an issue lately with whitelisting which the dev team is working to fix. Does your whitelisted urls have / at the end of it? If yes, could you try whitelisting the URLs without the / at the end.
No they do not have.
Has this issue been solved?
1 Like
Please try out the v7 sdk and let me know if the issue persists. By the way, I am emailing you. Let’s hop on a call some time and fix this.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.