Multiple connections

I have code like this.

const { StringSession } = require('telegram/sessions')
const input = require('input') // npm i input

const apiId = 111111
const apiHash = 'fcf............................'
const stringSession = new StringSession(''); // fill this later with the value from session.save()
(async () => {
    console.log('Loading interactive example...')
    const client = new TelegramClient(stringSession, apiId, apiHash, { connectionRetries: 5 })
    await client.start({
        phoneNumber: async () => await input.text('number ?'),
        password: async () => await input.text('password?'),
        phoneCode: async () => await input.text('Code ?'),
        onError: (err) => console.log(err),
    });
    console.log('You should now be connected.')
    console.log(client.session.save()) // Save this string to avoid logging in again
  async function eventPrint(event: NewMessageEvent) {
  console.log(event.message);
  };
  client.addEventHandler(eventPrint, new NewMessage({ chats: [chatId] }));
})()

When i run this code on express server in different por only work last telegram. That is, the last running one always works, the previous ones do not work. It feels like the new connection is killing the old one. How to solve the problem with multi-connection?

[painor]

you can’t run the same session multiple times. Telegram will only send updates to the latest running client.

if you want to receive updates you’ll need a new session for each client (even if it’s the same account).

[painor]

GramJS returns a SessionString that you can save in your DB if you want.

you can use the same session string in the same IP to send messages

You would need a different session string if you want to receive messages/updates. it’s a telegram limitation