Connection closed while receiving data

[ghost]

After a few hours, that disconnects whithout reason.

└── [email protected]

[painor]

Are you on the latest version? Node or browser? Did you do anything special in your code?

[vitalyster]

Same issue for me, on latest version

[Freihart512]

Same issue in node

[painor]

can you try the latest version?

[ghost]

Are you on the latest version? Node or browser? Did you do anything special in your code?

I didn't anything special in my code and I running Node

[Freihart512]

same issue with node 14 and telegram(gramjs) 2.9.2 (last version )

[MoKhajavi75]

Hey Same here:

telegram: 2.9.2
node: 16.15.1
System:
  Host: ZenBook Kernel: 5.15.0-40-generic x86_64 bits: 64
    Desktop: KDE Plasma 5.24.4 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)

cc @painor I'm on latest version and it's happening

[MoKhajavi75]

Fixed in latest

[Qionar]

I have same problem

telegram: 2.10.7 node: 14.16

[jeffersonveloso]

Same problem here. Any solution ?

[amrtn]

I'm experiencing the same problems with gram.js version 2.13.6

[Qionar]

Hi, I have solved this problem. In my case, the problem was that I connected user using the library for the client ( browser ), but the session hash was used on the server side

[MoKhajavi75]

Hi, I have solved this problem. In my case, the problem was that I connected user using the library for the client ( browser ), but the session hash was used on the server side

Can you please post some codes?

[MaxNamazov]

Hi, I have solved this problem. In my case, the problem was that I connected user using the library for the client ( browser ), but the session hash was used on the server side

I have the same issue, but actually, I want to do this intentionally (I want to create a session in the browser and then use this session string on the server). Is it possible?

[Qionar]

Hello, I'm not sure about this. I tried to do it, but it doesn't work right. If you use nodejs as backend part of your application, just use promises

[MaxNamazov]

@painor has already answered me in telegram and that's what he said:

they (sessions in the browser and on the server) are techincally compatible but you have to do some work to get them there. the reason that's happening is because browser (websocket) and node (normal sockets) use different api endpoints. You'd need to change this in the session to make it work. you can use setDC to do that

[Badisi]

Still facing this issue with gramjs 2.16.0 on browser.

Can we at least listen to this event somehow so I can logout my users nicely ? (because right now when they came back to my app they are just stuck due to the connection closed)

[mikiyasET]

Account deactivation and banned because of this 😢

[Raduc4]

@MaxNamazov You have mentioned that this error can be fixed with setDC, have you managed to fix it? Thanks

[Raduc4]

It was because of my internet network firewall