🐛🐛 session does not persist using LocalAuth id 🐛🐛 #2164

andresmv94 · 2023-04-21T16:39:56Z

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

I have been using "whatsapp-web.js" in my application for about 6 months, and yesterday the session persistence stopped working, I am using authStrategy: new LocalAuth({ clientId: user._id }), and with this When I want to use the WhatsApp channel again, I can use it without having to scan the QR again, but every time that I want to use the channel and send messages, it is making me to scan the QR and this was not happening until yesterday

Expected behavior

for first time scan the QR once, and be able to continue using whatsapp without having to scan each time I use it

Steps to Reproduce the Bug or Issue

configure the server in linux to work
configure whatsapp web js with authStrategy: new LocalAuth({ clientId: "some-client-id" })
scan the QR and send a message
reuse sending messages with the same "some-client-id"

Relevant Code

function authWhatsapp (user) => {
	console.log("init authentication");
	const client = await new Client({
      authStrategy: new LocalAuth({ clientId: user._id }), // user = {_id: "1234abc", name: "juan"}
      qrMaxRetries: 3,
      authTimeoutMs: 60000,
      puppeteer: {
        executablePath: process.env.CHROME_EXECUTABLE_PATH, // CHROME_EXECUTABLE_PATH=/usr/bin/google-chrome-stable
        args: ["--no-sandbox", "--disable-setuid-sandbox"],
      },
    });	
	
	client.on("qr", async (qr) => {
		console.log("scan qr");
		console.log(qr);		
		
    });
	
	 client.on("ready", async () => {
		console.log("Wapp web connected");
	 });
	
}

function sendWhatsapp (user) => {
	console.log("try send messages");
	client = await new Client({
      authStrategy: new LocalAuth({ clientId: user._id }), // user = {_id: "1234abc", name: "juan"}
      authTimeoutMs: 60000,
      puppeteer: {
        executablePath: process.env.CHROME_EXECUTABLE_PATH,  // CHROME_EXECUTABLE_PATH=/usr/bin/google-chrome-stable
        args: ["--no-sandbox", "--disable-setuid-sandbox"],
      },
    });
	
	 client.on("ready", async () => { // this is never executed 🫤
		console.log("perfect, your are authenticated, Wapp web connected");
		/*
			code to send messages...
		*/
	 });
	 
	 client.on("qr", async (qr) => {
		
		console.log("The whatsapp is asking for QR you are not authenticated");	
		console.log(qr);	
		
    });

}

for authWhatsapp function:

> init authentication
> scan qr
> 2@Zy5JBs9MeMX0GBeDlNd1....RUI9lbeATZGDNBtx52+29CIw=
> Wapp web connected

for sendWhatsapp function: 

> try send messages
> The whatsapp is asking for QR you are not authenticated
> 2@TYQbrQCmYVbCB0KG...dEy8edXIPh32AiME0=

Browser Type

Google Chrome

WhatsApp Account Type

Standard

Does your WhatsApp account have multidevice enabled?

Yes, I am using Multi Device

Environment

OS: Ubuntu 20
Phone OS:  Android, iOS
whatsapp-web.js version [1.19.5]
WhatsApp Web version [2.2317.10]:
Node.js Version [v19.8.1]

Additional context

remember: this was not happening until yesterday, I already tried setting all the permissions to the .wwebjs_auth folder, and to all its content, but it's still the same, I also notice that in windows (no server -> my personal computer) with exactly the same configuration but using CHROME_EXECUTABLE_PATH=C:/Program Files/Google/Chrome /Application/chrome.exe, it is working correctly, any idea why?

maybe the session files are not being saved correctly in the ".wwebjs_auth" folder, but I don't really know how to look at that part

Update: in other computer with Windows is happenig the same issue so is not the OS.

The text was updated successfully, but these errors were encountered:

benjachiban · 2023-04-21T19:17:12Z

I am experiencing the same problem.
I have been using it for a few weeks without a problem and since yesterday it has been disconnecting me often and it does not notify me why it happens. Anyone else with this error?

andresmv94 · 2023-04-21T22:31:03Z

The whatsapp version that whatsapp-web.js mark like "working with" is = WhatsApp_Web 2.2306.7, and Now the current WhatsApp Web version is 2.2317.10. maybe something with session was changed

I am experiencing the same problem. I have been using it for a few weeks without a problem and since yesterday it has been disconnecting me often and it does not notify me why it happens. Anyone else with this error?

benjachiban · 2023-04-23T02:31:11Z

The whatsapp version that whatsapp-web.js mark like "working with" is = WhatsApp_Web 2.2306.7, and Now the current WhatsApp Web version is 2.2317.10. maybe something with session was changed

I am experiencing the same problem. I have been using it for a few weeks without a problem and since yesterday it has been disconnecting me often and it does not notify me why it happens. Anyone else with this error?

Pudiste encontar solucion??

benjachiban · 2023-04-24T17:09:26Z

At first I found a solution, for now it's working. In the package.json inside node_modules/whatsapp-web... change the version of puppeteer to 18.1.0

andresmv94 · 2023-04-25T15:13:54Z

At first I found a solution, for now it's working. In the package.json inside node_modules/whatsapp-web... change the version of puppeteer to 18.1.0

Is weird because that works some times

RC047 · 2023-04-26T23:18:21Z

same here

samuelfaj · 2023-04-30T17:54:43Z

Same here

mahmouds12 · 2023-05-05T08:09:30Z

benjachiban

I tried it, didn't work

ch9ch9n · 2023-05-11T15:07:49Z

Same problem
change the version of puppeteer to 18.1.0 dont work

andresmv94 · 2023-05-15T23:23:53Z

@pedroslopez , some idea about this?

Neotastisch · 2023-05-22T14:18:46Z

same here

akimabs · 2023-05-23T15:58:18Z

same here :(

lanstat · 2023-05-23T22:50:47Z

At first I found a solution, for now it's working. In the package.json inside node_modules/whatsapp-web... change the version of puppeteer to 18.1.0

It worked for me, update puppeteer to 20.3.0

XxQuickSilverZz · 2023-05-24T12:45:49Z

At first I found a solution, for now it's working. In the package.json inside node_modules/whatsapp-web... change the version of puppeteer to 18.1.0

It worked for me, update puppeteer to 20.3.0

Please fulls steps. I need a npm install then?

iAndreas · 2023-05-24T16:35:49Z

My puppeteer is on version 20.3.0 but the error persists.

XxQuickSilverZz · 2023-05-24T17:25:48Z

@pedroslopez Maybe your help?

Santosl2 · 2023-07-25T20:38:07Z

up

Davixe7 · 2023-07-28T17:05:57Z

UP, session persistence is super unconsistent.

longgtruong · 2023-08-02T14:44:19Z

same problem

daniloavilez · 2023-08-04T12:38:36Z

I had the same problem with session in another library, it seems this problem is related to some thing that Whatsapp changed. Maybe it's a false impression I've tested different libraries.

leandrosantoss · 2023-08-04T12:45:04Z

Hi, I resolved it with permission chmod on both .wwebjs_auth and .wwebjs_cache directories

regards

bryanfok · 2023-08-06T06:44:42Z

Hi, I resolved it with permission chmod on both .wwebjs_auth and .wwebjs_cache directories

regards
chmod 777 .wwebjs_cache

still ask to scan qr code

Santosl2 · 2023-08-08T21:30:28Z

up again

mahmouds12 · 2023-09-14T08:43:35Z

still happening

Avivbens · 2024-02-19T15:26:11Z

We really need some solution in here...

I'm willing to assist, just give me the details of the potential issue 🙏

Avivbens · 2024-02-19T15:36:46Z

OK, I've managed to resolve the issue:

TL;DR
Set the webVersion to 2.2306.7

NestJS provider

export const WhatsappClientProvider: Provider<Client> = {
    provide: WHATSAPP_CLIENT,
    inject: [ConfigService],
    useFactory: async (configService: ConfigService) => {
        const logger: Logger = new Logger('WHATSAPP_CLIENT')
        const env = configService.get<Envs>(EnvVariables.NODE_ENV, Envs.Production)
        const args = env === Envs.Production ? ['--no-sandbox', '--disable-setuid-sandbox'] : undefined

        const client = new Client({
            authStrategy: new LocalAuth(),
            webVersion: '2.2306.7', // this keeps the Whatsapp Verison with the latest version worked 👍 
            puppeteer: {
                args,
            },
        })

        client.once('qr', (qr) => {
            logger.debug('QR code received, scan please')
            return qrcode.generate(qr)
        })

        client.on('authenticated', () => {
            logger.debug('Authenticated successfully!')
        })

        client.on('disconnected', (reason) => {
            logger.error(`Disconnected, reason: ${reason}`)
        })

        const prm = new Promise<void>((resolve) =>
            client.on('ready', async () => {
                logger.debug('WhatsApp Client is ready!')
                resolve()
            }),
        )

        client.initialize()


        await prm
        return client
    },
}

Terminal Screenshot

eduardotorresdev · 2024-02-20T17:05:34Z

@Avivbens, I tried but it didn't made it. Can you share the whatsapp-web.js version? Did you change the puppeteer version? Any help is very welcome.

Avivbens · 2024-02-20T17:17:46Z

@Avivbens, I tried but it didn't made it. Can you share the whatsapp-web.js version? Did you change the puppeteer version? Any help is very welcome.

Sure man 👍

Here are my deps versions:

Avivbens · 2024-02-20T17:19:46Z

@eduardotorresdev
BTW, let the connection to establish for a minute or two...

You'll see on your WhatsApp client over the device that your chats are in sync. Keep it that way for a bit, then test the restart.

eduardotorresdev · 2024-02-20T20:55:42Z

@Avivbens It's worked! Thank you. I just waited the time for WhatsApp client sync with device and, that's it, worked like charm.

Avivbens · 2024-02-20T21:15:46Z

@Avivbens It's worked! Thank you. I just waited the time for WhatsApp client sync with device and, that's it, worked like charm.

Happy to hear 🥳

For future documentation - list here the versions you're on please 🙏

eduardotorresdev · 2024-02-21T13:21:00Z

I'm using whatsapp-web.js at "^1.23.0" version. I didn't changed puppeteer version or of any related package to wwebjs lib. I just added the webVersion that you told previously.

eduardotorresdev · 2024-02-21T13:28:58Z

@Avivbens Can i colaborate with something? I believe that is very important to documentate all this question of auth and his persistance, so maybe we can do this together.

Avivbens · 2024-02-21T15:41:40Z

@Avivbens Can i colaborate with something? I believe that is very important to documentate all this question of auth and his persistance, so maybe we can do this together.

Well, that is a good idea.
Personally, I find GitHub issues part of the documentation, but we might add it into the official docs for such an important thing.

That being said, the documentation structure of this project isn't in its best shape.
The current documentation site is being generated by JsDocs, but I cannot see the content anywhere in the repo.

Maybe the owner can give us a hint here 👼

@pedroslopez

yairmelamed · 2024-02-22T08:39:13Z

OK, I've managed to resolve the issue:

TL;DR Set the webVersion to 2.2306.7

NestJS provider

export const WhatsappClientProvider: Provider<Client> = {
    provide: WHATSAPP_CLIENT,
    inject: [ConfigService],
    useFactory: async (configService: ConfigService) => {
        const logger: Logger = new Logger('WHATSAPP_CLIENT')
        const env = configService.get<Envs>(EnvVariables.NODE_ENV, Envs.Production)
        const args = env === Envs.Production ? ['--no-sandbox', '--disable-setuid-sandbox'] : undefined

        const client = new Client({
            authStrategy: new LocalAuth(),
            webVersion: '2.2306.7', // this keeps the Whatsapp Verison with the latest version worked 👍 
            puppeteer: {
                args,
            },
        })

        client.once('qr', (qr) => {
            logger.debug('QR code received, scan please')
            return qrcode.generate(qr)
        })

        client.on('authenticated', () => {
            logger.debug('Authenticated successfully!')
        })

        client.on('disconnected', (reason) => {
            logger.error(`Disconnected, reason: ${reason}`)
        })

        const prm = new Promise<void>((resolve) =>
            client.on('ready', async () => {
                logger.debug('WhatsApp Client is ready!')
                resolve()
            }),
        )

        client.initialize()


        await prm
        return client
    },
}

Terminal Screenshot

It doesn't help, it works for one week and then suddenly it disconnects and asks for qr again on restore with no reason.. how can we fix this?? why it's happening?

Avivbens · 2024-02-22T11:33:35Z

OK, I've managed to resolve the issue:
TL;DR Set the webVersion to 2.2306.7

NestJS provider

export const WhatsappClientProvider: Provider<Client> = {
    provide: WHATSAPP_CLIENT,
    inject: [ConfigService],
    useFactory: async (configService: ConfigService) => {
        const logger: Logger = new Logger('WHATSAPP_CLIENT')
        const env = configService.get<Envs>(EnvVariables.NODE_ENV, Envs.Production)
        const args = env === Envs.Production ? ['--no-sandbox', '--disable-setuid-sandbox'] : undefined

        const client = new Client({
            authStrategy: new LocalAuth(),
            webVersion: '2.2306.7', // this keeps the Whatsapp Verison with the latest version worked 👍 
            puppeteer: {
                args,
            },
        })

        client.once('qr', (qr) => {
            logger.debug('QR code received, scan please')
            return qrcode.generate(qr)
        })

        client.on('authenticated', () => {
            logger.debug('Authenticated successfully!')
        })

        client.on('disconnected', (reason) => {
            logger.error(`Disconnected, reason: ${reason}`)
        })

        const prm = new Promise<void>((resolve) =>
            client.on('ready', async () => {
                logger.debug('WhatsApp Client is ready!')
                resolve()
            }),
        )

        client.initialize()


        await prm
        return client
    },
}

Terminal Screenshot

It doesn't help, it works for one week and then suddenly it disconnects and asks for qr again on restore with no reason.. how can we fix this?? why it's happening?

Well, in general, the library has an Apache license, meaning it has no responsibility for the stability of the product.
I can just assume that Whatsapp servers can revoke client authentication based on its behavior.

That being said, you can try to use the RemoteAuth strategy, it might be a bit more stable.

yairmelamed · 2024-05-02T19:03:46Z

Hello every one.. is there a solution here? It is so frustrating.. It still happens..

josuelmm · 2024-05-20T23:02:39Z

Same problem

MikeSoft · 2024-07-02T01:48:22Z

up

ingGhost · 2024-08-07T14:53:02Z

how u can fix the issue?

AKwoKWH · 2024-09-02T15:55:29Z

having the same issue recently

luandro · 2024-10-11T01:49:09Z

Also having the same issue, any updates?

egiesem · 2024-10-24T13:37:11Z

any update?

MikeSoft · 2024-10-25T18:18:13Z

any update?

I updated to the last version "whatsapp-web.js": "1.26.1-alpha.2" and apparently it's solved.
const wa_client = new Client({authStrategy: new LocalAuth({ dataPath: "sessions" }),});

andresmv94 added the bug Something isn't working label Apr 21, 2023

andresmv94 changed the title ~~session does not persist using LocalAuth id~~ Apr 21, 2023

andresmv94 mentioned this issue May 8, 2023

Session is not persistent #2185

Closed

1 task

andresmv94 mentioned this issue Jul 4, 2023

.wwebjs_Auth login session #2326

Closed

1 task

This was referenced Dec 4, 2023

session not load correctly anymore session -LocalAuth #2231

Closed

Unable to restore authenticated sessions in LocalAuth Strategy #1446

Closed

This was referenced Mar 22, 2024

Client is disconnecting automatically after 2 or 3 days #2833

Closed

Session closes after 1 month #2005

Closed

QR Code disconnects too often #1451

Closed

alechkos mentioned this issue Mar 30, 2024

Local Authentication Issue #2854

Closed

1 task

alechkos mentioned this issue May 31, 2024

Losing Connection After a Few Days and Needing to Scan QR Code Again #3070

Closed

1 task

MikelCalvo mentioned this issue Jun 19, 2024

Added session persistence Zain-ul-din/whatsapp-ai-bot#45

Merged

alechkos mentioned this issue Jul 24, 2024

Persistent Session Troubles: wahtsapp-web.js Disconnects After 2-3 days #3224

Closed

1 task

Repository owner deleted a comment from Hasnen-mr Sep 14, 2024

alechkos mentioned this issue Sep 21, 2024

Whatsapp Desconectando sozinho após 10 segundos. #3285

Closed

1 task

luandro mentioned this issue Oct 11, 2024

Requests QR code at all times WAppAI/assistant#294

Open

🐛🐛 session does not persist using LocalAuth id 🐛🐛 #2164

🐛🐛 session does not persist using LocalAuth id 🐛🐛 #2164

Comments

andresmv94 commented Apr 21, 2023 • edited Loading

Is there an existing issue for this?

Describe the bug

Expected behavior

Steps to Reproduce the Bug or Issue

Relevant Code

Browser Type

WhatsApp Account Type

Does your WhatsApp account have multidevice enabled?

Environment

Additional context

Update: in other computer with Windows is happenig the same issue so is not the OS.

benjachiban commented Apr 21, 2023

andresmv94 commented Apr 21, 2023

benjachiban commented Apr 23, 2023

benjachiban commented Apr 24, 2023

andresmv94 commented Apr 25, 2023 • edited Loading

RC047 commented Apr 26, 2023

samuelfaj commented Apr 30, 2023

mahmouds12 commented May 5, 2023

ch9ch9n commented May 11, 2023 • edited Loading

andresmv94 commented May 15, 2023

Neotastisch commented May 22, 2023

akimabs commented May 23, 2023

lanstat commented May 23, 2023

XxQuickSilverZz commented May 24, 2023

iAndreas commented May 24, 2023

XxQuickSilverZz commented May 24, 2023

Santosl2 commented Jul 25, 2023

Davixe7 commented Jul 28, 2023

longgtruong commented Aug 2, 2023

daniloavilez commented Aug 4, 2023 • edited Loading

leandrosantoss commented Aug 4, 2023

bryanfok commented Aug 6, 2023

Santosl2 commented Aug 8, 2023

mahmouds12 commented Sep 14, 2023

Avivbens commented Feb 19, 2024

Avivbens commented Feb 19, 2024 • edited Loading

NestJS provider

Terminal Screenshot

eduardotorresdev commented Feb 20, 2024

Avivbens commented Feb 20, 2024

Avivbens commented Feb 20, 2024

eduardotorresdev commented Feb 20, 2024

Avivbens commented Feb 20, 2024

eduardotorresdev commented Feb 21, 2024

eduardotorresdev commented Feb 21, 2024

Avivbens commented Feb 21, 2024

yairmelamed commented Feb 22, 2024 • edited Loading

NestJS provider

Terminal Screenshot

Avivbens commented Feb 22, 2024

NestJS provider

Terminal Screenshot

yairmelamed commented May 2, 2024

josuelmm commented May 20, 2024

MikeSoft commented Jul 2, 2024

ingGhost commented Aug 7, 2024 • edited by alechkos Loading

AKwoKWH commented Sep 2, 2024

luandro commented Oct 11, 2024

egiesem commented Oct 24, 2024

MikeSoft commented Oct 25, 2024

andresmv94 commented Apr 21, 2023 •

edited

Loading

andresmv94 commented Apr 25, 2023 •

edited

Loading

ch9ch9n commented May 11, 2023 •

edited

Loading

daniloavilez commented Aug 4, 2023 •

edited

Loading

Avivbens commented Feb 19, 2024 •

edited

Loading

yairmelamed commented Feb 22, 2024 •

edited

Loading

ingGhost commented Aug 7, 2024 •

edited by alechkos

Loading