# \[Archive\] Cannot authenticateUser, even though I can still get user info

**URL:** <https://builder.metamask.io/t/archive-cannot-authenticateuser-even-though-i-can-still-get-user-info/1061>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [March 3, 2025, 10:41am UTC](https://builder.metamask.io/t/archive-cannot-authenticateuser-even-though-i-can-still-get-user-info/1061 "2025-03-03T10:41:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![toandq](https://avatars.discourse-cdn.com/v4/letter/t/8e8cbc/32.png) [@toandq](https://builder.metamask.io/u/toandq)\
**Post date:** [March 3, 2025, 10:41am UTC](https://builder.metamask.io/t/archive-cannot-authenticateuser-even-though-i-can-still-get-user-info/1061/1 "2025-03-03T10:41:22Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **toandq** on 3/3/2025.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

When asking for help in this category, please make sure to provide the following details:

- SDK Version: 9.4.0
- Platform: Web
- Browser Console Screenshots:  

[![Screenshot 2025-03-03 at 17.38.20](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/c0e8b6540f33b4199f49464afcfe089a80aff5e6.png)
Screenshot 2025-03-03 at 17.38.201470×90 10.2 KB
](https://web3auth.io/community/uploads/default/original/2X/6/6530508ea59f4e366b0753cc82272a67cc314a0d.png "Screenshot 2025-03-03 at 17.38.20")

I followed the guide here [How to use NextAuth with Web3Auth | Web3Auth](https://web3auth.io/docs/guides/next-auth). I was able to connect, and get private key, get userInfo. However, when I want to get the id token for backend verification by calling authenticateUser, the above error occur

---

<div class="post-metadata">

**Author:** ![w3abot](https://avatars.discourse-cdn.com/v4/letter/w/4da419/32.png) [@w3abot](https://builder.metamask.io/u/w3abot)\
**Post date:** [March 3, 2025, 10:43am UTC](https://builder.metamask.io/t/archive-cannot-authenticateuser-even-though-i-can-still-get-user-info/1061/2 "2025-03-03T10:43:02Z")

</div>

Hello! Thanks for reaching out.

Based on your message, you’re working with the Single Factor Auth Web SDK (version 9.4.0) on a web platform. You’ve managed to connect and retrieve the private key and user info, but you’re encountering an issue when calling `authenticateUser` to get the ID token for backend verification.

To assist further, could you please share:

1. The code snippets of your Web3Auth initialization and login process?
2. The specific error message displayed in the browser console from your screenshot?
3. The verifier name, method of login, and authentication details to understand if it’s related to custom authentication.

This information will help us troubleshoot the issue more effectively. Thank you for your patience!

> Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

> Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. [Web3Auth Developer Office Hours](https://web3auth.io/community/t/web3auth-developer-office-hours/8777)

---

<div class="post-metadata">

**Author:** ![yashovardhan](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/yashovardhan/32/1526_2.png) [@yashovardhan](https://builder.metamask.io/u/yashovardhan)\
**Post date:** [March 27, 2025, 2:30pm UTC](https://builder.metamask.io/t/archive-cannot-authenticateuser-even-though-i-can-still-get-user-info/1061/3 "2025-03-27T14:30:08Z")

</div>

Hey @toandq

This issue looks to be happening because of your RPC URL. Please use a production RPC URL from a service like Infura ([https://infura.io](https://infura.io))