# \[Archive\] Something went wrong, unable to connect to web3auth

**URL:** <https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [November 2, 2023, 5:30am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706 "2023-11-02T05:30:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 5:30am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/1 "2023-11-02T05:30:23Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **keyspace.dev** on 11/2/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

**Please provide the following details too when asking for help in this category:**

I’m having issue connecting to Web3Auth from all my environments, either the modal doesn’t load the inputs at all or it says something went wrong. can you please tell me the issue:

In local and dev environment, modal shows, but when try to connect to web3auth the popup does not connect

In production, environment the modal doesn’t show up at all

[![Screenshot 2023-11-01 at 22.29.53](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/e/eca539149abe033b93df5f315b71381da6a6580c.jpeg)
Screenshot 2023-11-01 at 22.29.532450×1520 181 KB
](https://web3auth.io/community/uploads/default/original/2X/f/ffe4a9b4eb169725a08dd58375c5255fa9df149c.jpeg "Screenshot 2023-11-01 at 22.29.53")
  

[![Screenshot 2023-11-01 at 22.29.45](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/7/73222b5af20cafc7874f78b68c6e425c07bac04d.jpeg)
Screenshot 2023-11-01 at 22.29.451920×1267 220 KB
](https://web3auth.io/community/uploads/default/original/2X/5/5201136438b2bea0e5467ee50ee2e3827dbb3ecb.jpeg "Screenshot 2023-11-01 at 22.29.45")

- SDK Version: ^5.2.0
- Verifier Details:
  - Verifier Name: KeySpace-App
  - JWKS Endpoint: not sure
  - Sample idToken(JWT): not sure

---

<div class="post-metadata">

**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\
**Post date:** [November 2, 2023, 5:44am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/2 "2023-11-02T05:44:20Z")

</div>

Hey there, welcome aboard! The error screen states that you have put a client id that’s for a project on testnet while you are setting the `web3AuthNetwork` parameter as mainnet. Please set it as testnet and let me know if this issue persists.

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 5:48am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/3 "2023-11-02T05:48:01Z")

</div>

Hey @keyspace.dev, let’s avoid posting the same question on multiple threads in the community. We want to create a helpful and supportive space for everyone to seek assistance.

I have replied here too.

Thanks and Welcome to Web3Auth Community

> [@Getting Error: \[could not retrieve access structure: not found\]](https://web3auth.io/community/t/getting-error-could-not-retrieve-access-structure-not-found/6110/9):
>
> Hey @keyspace.dev Please always create a new Topic when asking for help, especially when a topic is marked solved. This is to avoid unnecessary notifications to the initial people in this thread. For this, as it says, the clientId belongs to the testnet network, and the app is configured to use the mainnet. Please use the same network client as what’s in the code.

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 5:51am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/4 "2023-11-02T05:51:04Z")

</div>

Yes I done that but now I have a world of new issues like this:

[![Screenshot 2023-11-01 at 22.50.53](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/d/d56a5b8dd20031324ffe45faca2c54835b461b93.jpeg)
Screenshot 2023-11-01 at 22.50.531920×1191 68.6 KB
](https://web3auth.io/community/uploads/default/original/2X/9/91ee0811b262c415ddd0c369c41b7ec59b4d5cad.jpeg "Screenshot 2023-11-01 at 22.50.53")

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 5:52am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/5 "2023-11-02T05:52:59Z")

</div>

Noted but this did not solve the core issue unfortunately

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 5:53am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/6 "2023-11-02T05:53:56Z")

</div>

Please share the initialization and login code snippet. Looks like a misconfig.

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 5:55am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/7 "2023-11-02T05:55:31Z")

</div>

here you are

this is for version:  
“@web3auth/base”: “^5.2.0”,  
“@web3auth/metamask-adapter”: “^5.2.0”,  
“@web3auth/modal”: “^5.2.0”,  
“@web3auth/web3auth”: “^1.1.4”,

```auto
//web3Auth.js
import { Web3Auth } from "@web3auth/modal";
// import { Web3Auth } from "@web3auth/web3auth";
import { CHAIN_NAMESPACES, WALLET_ADAPTERS } from "@web3auth/base";
import { OpenloginAdapter } from "@web3auth/openlogin-adapter";
import { MetamaskAdapter } from "@web3auth/metamask-adapter";
import Web3 from "web3";
import logo from "./favicon-32x32.png";
const clientId = process.env.REACT_APP_WEB3AUTH_CLIENT_ID;
export const modalConfigLogins = {
label: “openlogin”,
loginMethods: {
sms_passwordless: { showOnModal: true },
google: {
showOnModal: false,
name: “Google Login”, // The desired name you want to show on the login button
//verifier: “YOUR_GOOGLE_VERIFIER_NAME”, // Please create a verifier on the developer dashboard and pass the name here
typeOfLogin: “google”, // Pass on the login provider of the verifier you’ve created
//clientId: “GOOGLE_CLIENT_ID.apps.googleusercontent.com”, // use your app client id you got from google
},
facebook: {
name: “Facebook Login”,
showOnModal: false,
},
twitter: {
name: “Twitter Login”,
showOnModal: false,
},
reddit: {
name: “Reddit Login”,
showOnModal: false,
},
discord: {
name: “Discord Login”,
showOnModal: false,
},
twitch: {
name: “Twitch Login”,
showOnModal: false,
},
apple: {
name: “Apple Login”,
showOnModal: false,
},
line: {
showOnModal: false,
},
github: {
name: “Github Login”,
showOnModal: false,
},
kakao: {
showOnModal: false,
},
linkedin: {
name: “LinkedIn Login”,
showOnModal: false,
},
weibo: {
showOnModal: false,
},
wechat: {
showOnModal: false,
},
},
};
export const fetchChainId = (chain) => {
if (chain === “Ethereum”) {
return “0x5”;
} else if (chain === “Polygon”) {
return “0x13881”;
}
};
export const web3auth = new Web3Auth({
clientId,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: process.env.REACT_APP_ETH_CHAIN_ID, //currently on Goerli test net “0x1”: ETHEREUM
rpcTarget: process.env.REACT_APP_ALCHEMY_URL_ETH,
},
authMode: “DAPP”,
uiConfig: {
theme: “light”,
appLogo: logo,
},
});
export const web3authPolygon = new Web3Auth({
clientId,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: process.env.REACT_APP_POLYGON_CHAIN_ID,
rpcTarget: process.env.REACT_APP_ALCHEMY_URL_POLYGON,
},
authMode: “DAPP”,
uiConfig: {
theme: “light”,
appLogo: logo,
},
});
export const metamaskAdapter = new MetamaskAdapter({
clientId,
sessionTime: 3600, // 1 hour in seconds
web3AuthNetwork: “cyan”,
});
export const openloginAdapter = new OpenloginAdapter({
adapterSettings: {
clientId,
network: “mainnet”,
uxMode: “popup”,
whiteLabel: {
name: “Keyspace Studio”,
logoLight: “logo”,
logoDark: “logo”,
defaultLanguage: “en”,
dark: false, // whether to enable dark mode. defaultValue: false
},
},
});
//Web3Auth old modal
export async function connectWallet(chain) {
console.log(“connecting to web3 t3”)
console.log(“chain”, chain)
if (chain === “Ethereum”) {
console.log(“web3auth initialized?”, web3auth)
if (!web3auth) {
console.log(“Web3Auth not initialized yet”);
return;
}
const walletProvider = await web3auth.connect();
console.log("web3auth walletProvider", walletProvider)

const caller = new Web3(walletProvider);
console.log("web3auth caller", caller)

const accounts = await caller.eth.getAccounts();
console.log("web3auth accounts", accounts)

const user = await web3auth.getUserInfo();
console.log("web3auth user", user)

let email = null;

if (user.email !== undefined &amp;&amp; user.email !== null &amp;&amp; user.email !== "") {
  email = user.email;
}

return [accounts[0], caller, email];

} else if (chain === “Polygon”) {
console.log(“web3authPolygon initialized?”, web3authPolygon)
if (!web3authPolygon) {
console.log(“Web3Auth not initialized yet”);
return;
}
const walletProvider = await web3authPolygon.connect();
const caller = new Web3(walletProvider);
const accounts = await caller.eth.getAccounts();

const user = await web3authPolygon.getUserInfo();

let email = null;

if (user.email !== undefined &amp;&amp; user.email !== null &amp;&amp; user.email !== "") {
  email = user.email;
}

return [accounts[0], caller, email];

}
}
//Web3Auth integration
export async function connectWallet1(chain) {
try {
if (chain === “Ethereum”) {
if (!web3auth) {
return;
}
////web3auth.configureAdapter(openloginAdapter);
  const walletProvider = await web3auth.connect();

  const caller = new Web3(walletProvider);

  const accounts = await caller.eth.getAccounts();

  const user = await web3auth.getUserInfo();

  let email = null;

  if (
    user.email !== undefined &amp;&amp;
    user.email !== null &amp;&amp;
    user.email !== ""
  ) {
    email = user.email;
  }

  return [accounts[0], caller, email];
} else if (chain === "Polygon") {
  if (!web3authPolygon) {
    return;
  }
  console.log("web3authPolygon", web3authPolygon)
  const walletProvider = await web3authPolygon.connect();
  console.log("walletProvider", walletProvider)

  const caller = new Web3(walletProvider);
  const accounts = await caller.eth.getAccounts();

  const user = await web3authPolygon.getUserInfo();

  let email = null;

  if (
    user.email !== undefined &amp;&amp;
    user.email !== null &amp;&amp;
    user.email !== ""
  ) {
    email = user.email;
  }

  return [accounts[0], caller, email];
}

} catch (e) {
console.log(e);
}
}

```

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 5:57am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/8 "2023-11-02T05:57:55Z")

</div>

Hey @keyspace.dev

Please upgrade these to the latest versions.

> [@keyspace.dev](#):
>
> “@web3auth/base”: “^5.2.0”,  
> “@web3auth/metamask-adapter”: “^5.2.0”,  
> “@web3auth/modal”: “^5.2.0”,  
> “@web3auth/web3auth”: “^1.1.4”,

Also, `@web3auth/web3auth` is deprecated, and `@web3auth/modal` is being used now, which I also see on your package.json file. Please remove `@web3auth/web3auth` and update all to the latest.

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 5:58am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/9 "2023-11-02T05:58:46Z")

</div>

Okay and what about the 413 error?

that’s using the 7.0.4 modal and it’s still breaking. I even upgraded to growth package and still breaks.

Secondly @shahbaz , how would my code change if I upgrade to the latest package? will I expect more breakages?

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 5:59am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/10 "2023-11-02T05:59:37Z")

</div>

> [@keyspace.dev](#):
>
> Okay and what about the 413 error?

This might be because of this, upgrading to the latest package will solve these issue.

> [@\[IMP!\] Web3Auth v5 sunset date](https://web3auth.io/community/t/imp-web3auth-v5-sunset-date/5507):
>
> Please note that Web3Auth (modal, no-modal, sfa-web) v5 and TorusWallet v1 will be sunset by the end of October. Google Chrome v116 update might cause issues along with v5 and the fixes for the same are released with v6 and v7. We recommend the users to upgrade to the latest version i.e. web v7. Additionally, please note that the end-of-life for v6 is scheduled to be 31st December 2023,

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 6:02am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/11 "2023-11-02T06:02:19Z")

</div>

What modifications would I need to make for my react code?

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 6:03am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/12 "2023-11-02T06:03:31Z")

</div>

Please follow the following migration guides:

 ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/4bea15d5fdfd372b2e7fae21263c61fab3da9379.png)

```
  <a href="https://web3auth.io/docs/pnp/migration-guides/modal-v5-to-v6" target="_blank" rel="noopener">web3auth.io</a>

```

### [PnP Modal SDK - v5 to v6 | Documentation | Web3Auth](https://web3auth.io/docs/pnp/migration-guides/modal-v5-to-v6)

PnP Modal SDK - v5 to v6 | Documentation - Web3Auth

 ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/4bea15d5fdfd372b2e7fae21263c61fab3da9379.png)

```
  <a href="https://web3auth.io/docs/pnp/migration-guides/modal-v6-to-v7" target="_blank" rel="noopener">web3auth.io</a>

```

### [PnP Modal SDK - v6 to v7 | Documentation | Web3Auth](https://web3auth.io/docs/pnp/migration-guides/modal-v6-to-v7)

PnP Modal SDK - v6 to v7 | Documentation - Web3Auth

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 6:07am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/13 "2023-11-02T06:07:39Z")

</div>

> [@shahbaz](#):
>
> [PnP Modal SDK - v5 to v6 | Documentation | Web3Auth](https://web3auth.io/docs/pnp/migration-guides/modal-v5-to-v6)

[![Screenshot 2023-11-01 at 23.06.42](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/e/ec6ee90c82820599491c033822f8327a2f1867da.jpeg)
Screenshot 2023-11-01 at 23.06.421920×1300 110 KB
](https://web3auth.io/community/uploads/default/original/2X/e/e9104f5905bb84b924260f6d23381e4604aa65d9.jpeg "Screenshot 2023-11-01 at 23.06.42")

I am still receiving the same 413 error:

my new packages:

“@walletconnect/client”: “^1.8.0”,  
“@web3auth/base”: “^7.0.4”,  
“@web3auth/ethereum-provider”: “^7.0.4”,  
“@web3auth/metamask-adapter”: “^7.0.4”,  
“@web3auth/modal”: “^7.0.4”,  
“@web3auth/single-factor-auth”: “^7.0.1”,  
“amazon-cognito-identity-js”: “^5.2.8”,

my react code now:

```auto
import { Web3Auth } from "@web3auth/modal";
// import { Web3Auth } from "@web3auth/web3auth";
import { CHAIN_NAMESPACES, WALLET_ADAPTERS } from "@web3auth/base";
import { OpenloginAdapter } from "@web3auth/openlogin-adapter";
import { MetamaskAdapter } from "@web3auth/metamask-adapter";
import Web3 from "web3";
import logo from "./favicon-32x32.png";
const clientId = process.env.REACT_APP_WEB3AUTH_CLIENT_ID;
export const modalConfigLogins = {
label: “openlogin”,
loginMethods: {
sms_passwordless: { showOnModal: true },
google: {
showOnModal: false,
name: “Google Login”, // The desired name you want to show on the login button
//verifier: “YOUR_GOOGLE_VERIFIER_NAME”, // Please create a verifier on the developer dashboard and pass the name here
typeOfLogin: “google”, // Pass on the login provider of the verifier you’ve created
//clientId: “GOOGLE_CLIENT_ID.apps.googleusercontent.com”, // use your app client id you got from google
},
facebook: {
name: “Facebook Login”,
showOnModal: false,
},
twitter: {
name: “Twitter Login”,
showOnModal: false,
},
reddit: {
name: “Reddit Login”,
showOnModal: false,
},
discord: {
name: “Discord Login”,
showOnModal: false,
},
twitch: {
name: “Twitch Login”,
showOnModal: false,
},
apple: {
name: “Apple Login”,
showOnModal: false,
},
line: {
showOnModal: false,
},
github: {
name: “Github Login”,
showOnModal: false,
},
kakao: {
showOnModal: false,
},
linkedin: {
name: “LinkedIn Login”,
showOnModal: false,
},
weibo: {
showOnModal: false,
},
wechat: {
showOnModal: false,
},
},
};
export const fetchChainId = (chain) => {
if (chain === “Ethereum”) {
return “0x5”;
} else if (chain === “Polygon”) {
return “0x13881”;
}
};
export const web3auth = new Web3Auth({
clientId,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: process.env.REACT_APP_ETH_CHAIN_ID, //currently on Goerli test net “0x1”: ETHEREUM
rpcTarget: process.env.REACT_APP_ALCHEMY_URL_ETH,
},
authMode: “DAPP”,
uiConfig: {
theme: “light”,
appLogo: logo,
},
});
export const web3authPolygon = new Web3Auth({
clientId,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: process.env.REACT_APP_POLYGON_CHAIN_ID,
rpcTarget: process.env.REACT_APP_ALCHEMY_URL_POLYGON,
},
authMode: “DAPP”,
uiConfig: {
theme: “light”,
appLogo: logo,
},
});
export const metamaskAdapter = new MetamaskAdapter({
clientId,
sessionTime: 3600, // 1 hour in seconds
web3AuthNetwork: “cyan”,
});
export const openloginAdapter = new OpenloginAdapter({
adapterSettings: {
clientId,
network: “mainnet”,
uxMode: “popup”,
whiteLabel: {
name: “Keyspace Studio”,
logoLight: “logo”,
logoDark: “logo”,
defaultLanguage: “en”,
dark: false, // whether to enable dark mode. defaultValue: false
},
},
});
//Web3Auth old modal
export async function connectWallet(chain) {
console.log(“connecting to web3 t3”)
console.log(“chain”, chain)
if (chain === “Ethereum”) {
console.log(“web3auth initialized?”, web3auth)
if (!web3auth) {
console.log(“Web3Auth not initialized yet”);
return;
}
const walletProvider = await web3auth.connect();
console.log("web3auth walletProvider", walletProvider)

const caller = new Web3(walletProvider);
console.log("web3auth caller", caller)

const accounts = await caller.eth.getAccounts();
console.log("web3auth accounts", accounts)

const user = await web3auth.getUserInfo();
console.log("web3auth user", user)

let email = null;

if (user.email !== undefined &amp;&amp; user.email !== null &amp;&amp; user.email !== "") {
  email = user.email;
}

return [accounts[0], caller, email];

} else if (chain === “Polygon”) {
console.log(“web3authPolygon initialized?”, web3authPolygon)
if (!web3authPolygon) {
console.log(“Web3Auth not initialized yet”);
return;
}
const walletProvider = await web3authPolygon.connect();
const caller = new Web3(walletProvider);
const accounts = await caller.eth.getAccounts();

const user = await web3authPolygon.getUserInfo();

let email = null;

if (user.email !== undefined &amp;&amp; user.email !== null &amp;&amp; user.email !== "") {
  email = user.email;
}

return [accounts[0], caller, email];

}
}
//Web3Auth integration
export async function connectWallet1(chain) {
try {
if (chain === “Ethereum”) {
if (!web3auth) {
return;
}
////web3auth.configureAdapter(openloginAdapter);
  const walletProvider = await web3auth.connect();

  const caller = new Web3(walletProvider);

  const accounts = await caller.eth.getAccounts();

  const user = await web3auth.getUserInfo();

  let email = null;

  if (
    user.email !== undefined &amp;&amp;
    user.email !== null &amp;&amp;
    user.email !== ""
  ) {
    email = user.email;
  }

  return [accounts[0], caller, email];
} else if (chain === "Polygon") {
  if (!web3authPolygon) {
    return;
  }
  console.log("web3authPolygon", web3authPolygon)
  const walletProvider = await web3authPolygon.connect();
  console.log("walletProvider", walletProvider)

  const caller = new Web3(walletProvider);
  const accounts = await caller.eth.getAccounts();

  const user = await web3authPolygon.getUserInfo();

  let email = null;

  if (
    user.email !== undefined &amp;&amp;
    user.email !== null &amp;&amp;
    user.email !== ""
  ) {
    email = user.email;
  }

  return [accounts[0], caller, email];
}

} catch (e) {
console.log(e);
}
}

```

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 6:19am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/14 "2023-11-02T06:19:53Z")

</div>

Are you experiencing issues only with email-passwordless login? Although you have disabled other login methods, can you please test enabling any other social login to see if it works?

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 6:28am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/15 "2023-11-02T06:28:10Z")

</div>

> [@keyspace.dev](#):
>
> `logo`

Please share the logo URL. Also, once try without this logo.

---

<div class="post-metadata">

**Author:** ![ty1](https://avatars.discourse-cdn.com/v4/letter/t/45deac/32.png) [@ty1](https://builder.metamask.io/u/ty1)\
**Post date:** [November 2, 2023, 6:33am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/16 "2023-11-02T06:33:17Z")

</div>

Okay first off you guys, I’m very disappointed in this app and all the frustrations it’s been causing I had to create another account because I reached a daily limit… like what!??

[![Screenshot 2023-11-01 at 23.23.01](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/4/4bf86ce43acf456493915060e9fb3b384ed78486.jpeg)
Screenshot 2023-11-01 at 23.23.011920×1300 94.1 KB
](https://web3auth.io/community/uploads/default/original/2X/6/63d8a1b4e00c6c1c20c895ba6e13a0657239a4b1.jpeg "Screenshot 2023-11-01 at 23.23.01")

Secondly, This issue has been occurring for email-passwordless & sms-passwordless.

I activated Google login to tried to login and I received this error:

[![Screenshot 2023-11-01 at 23.33.08](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/53fb6126fbbe63524b149f3b5fae9257415401c2.jpeg)
Screenshot 2023-11-01 at 23.33.081920×1300 227 KB
](https://web3auth.io/community/uploads/default/original/2X/5/5fa15d94c06a70a307a9e6cf766853f1e5402708.jpeg "Screenshot 2023-11-01 at 23.33.08")

Thirdly, I have removed the logo and received another error with email-password:

[![Screenshot 2023-11-01 at 23.35.24](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/7/7587fce3582859b17f6103743c0ebcba368e617d.jpeg)
Screenshot 2023-11-01 at 23.35.241920×1300 99.6 KB
](https://web3auth.io/community/uploads/default/original/2X/c/c7e9d70fb8ffbb7f76533d00e4d3ec8b3a509fc0.jpeg "Screenshot 2023-11-01 at 23.35.24")

@shahbaz@maharshi

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 6:40am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/17 "2023-11-02T06:40:41Z")

</div>

Hey @ty1 and @keyspace.dev,

I apologize for any inconvenience you may have experienced. The message you received was to prevent spam on the community. I checked and found that your previous account had exceeded the limit, which is why you were seeing this message. However, I will increase the limits to allow you to continue using the community using your previous account. Please understand that this measure is necessary to ensure that the community remains free of spam.

Thank you for trying the suggested approach. I will share this with the engineering team and get back to you at earliest.

---

<div class="post-metadata">

**Author:** ![ty1](https://avatars.discourse-cdn.com/v4/letter/t/45deac/32.png) [@ty1](https://builder.metamask.io/u/ty1)\
**Post date:** [November 2, 2023, 6:41am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/18 "2023-11-02T06:41:40Z")

</div>

I was hoping for something soon as we have an event tomorrow but okay.

---

<div class="post-metadata">

**Author:** ![keyspace.dev](https://avatars.discourse-cdn.com/v4/letter/k/2bfe46/32.png) [@keyspace.dev](https://builder.metamask.io/u/keyspace.dev)\
**Post date:** [November 2, 2023, 7:00am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/19 "2023-11-02T07:00:00Z")

</div>

What should I do in the mean time?

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [November 2, 2023, 7:32am UTC](https://builder.metamask.io/t/archive-something-went-wrong-unable-to-connect-to-web3auth/1706/20 "2023-11-02T07:32:22Z")

</div>

Hey @keyspace.dev,

Please be informed that our team will be reaching out to you via email to provide you with the necessary assistance. Kindly keep an eye out for their message.