We are getting the below errors while authentication although the issue was working one day ago without any change from our side. It looks like the webhooks for authentication are broken.
Note that the Web3Auth dashboard is working fine and all parameters are working correctly. Is there any changes that we should be made aware of?
@georgeschouchani1 Welcome Aboard!
Which SDK are you using for your Dapp Web Modal or No Modal? Are you on the latest version?
I see from the logs this error from API api.eumlet.com/api/v1/finance/lean/customer/:1 Failed to load resource: the server responded with a status of 403 ()
Could you share your implementation code so our team can check?
This is after the fact of authentication, it is returning 403 because it did not authenticate. We are using the no modal as the SDK. The implementation is pretty long and integrated into our authentication process as well. We tried with multiple browsers, VPN as well as different websites with the same authentacation process. Worst part is that yesterday everything was working fine.
1 Like
Also in the logs it shows invalid public key for this link:
https://broadcast-server.tor.us/store/get?key=
(omitted the public key not sure if I should shre it) with a 404 error. Could that also be part of the issue?
1 Like
@georgeschouchani1 Are you on the latest Web3Auth version 6.1.7? You should not face any issue on the latest version.
Regarding this error, our team confirmed it is safe to ignore it.
After doing this an error I get:
There seems to be some bug in the code. Please contact support to fix this.
could not validate redirect, please whitelist your domain: https://login.eumlet.com for provided clientId ### (I removed it) at https://dashboard.web3auth.io. Also, this project is on mainnet network. Please ensure the the used Client ID belongs to this network.
Although we are 100% that this domain is whitelisted for the clientID we have.
Have you specified the web3AuthNetwork parameter during the Web3Auth initialization ? I’ll paste a snippet here for your reference on where should it go. Please mention the network you are on Testnet, Mainnet, etc whichever you have setup up on the dashboard should match with the network in your code too. Sample code below:
import { Web3AuthNoModal } from "@web3auth/no-modal";
import { CHAIN_NAMESPACES } from "@web3auth/base";
const web3auth = new Web3AuthNoModal({
clientId: "YOUR_WEB3AUTH_CLIENT_ID",
web3AuthNetwork: "mainnet",
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155, // SOLANA, OTHER
chainId: "0x1",
},
});
Yes I have added the web3AuthNetwork as well for mainnet.
We are currently using modal as shown here:
const web3AuthInstance = new Web3Auth({
chainConfig: chainConfig,
enableLogging: true,
clientId: clientId,
sessionTime: SESSION_TIME,
web3AuthNetwork: isMainnet ? "mainnet" : "testnet",
});
const sdkInstance = new OpenLogin({
clientId: clientId,
network: web3AuthNetwork,
uxMode: "popup",
});
const adapter = new OpenloginAdapter({
adapterSettings: {
clientId: clientId,
network: web3AuthNetwork,
uxMode: "popup",
},
});
web3AuthInstance.configureAdapter(adapter);
await web3AuthInstance.initModal();
Please share the console logs from the page where you get the error
There seems to be some bug in the code
Error: could not validate redirect, please whitelist your domain: X (redacted) for provided clientId #xxx# (redacted) at https://dashboard.web3auth.io.
Also, this project is on mainnet network. Please ensure the the used Client ID belongs to this network.
at h (start.5dbf422b.js:1:496)
at m (start.5dbf422b.js:1:1330)
at async Proxy.created (start.5dbf422b.js:1:7519)
We are sure that it is whitelisted, and we tried removing and readding it as well!
Were you able to check the issue?
The issue is being looked into by our dev team and you will receive further updates once resolved.
Hope we can solve this fast since all our users are locked up due to this error. Its pretty weird.
Not sure what you mean by sample Id token, but the clientID is: BG2rhOf_J6-i_BkV6gN2LDP2GNqx94g45RF3HEEdkCcEjEPYJz_et2nqL4kBa-UOqSjGDr7UUOnIBE1kazezXJQ
and for the verifier name we are using Plug and Play and tried Google, as well as email-passwordless
Hope this helps with resolving the issue, for sample ID token we cannot generate one due to the issue so not sure how can I get one across here.