CANNOT GET A SIGNIN CODE

[d-kobzar]

Does it work still ? I cannot get code for 2 days, the scripts says it's sent, but I don't have it on Telegram ...
Here is log, hope someone could help

Loading interactive example...
[2026-06-18T09:25:57.695] [INFO] - [Running gramJS version 2.25.10]
[2026-06-18T09:25:57.696] [INFO] - [Connecting to 149.154.167.91:80/TCPFull...]
[2026-06-18T09:25:59.197] [INFO] - [Connection to 149.154.167.91:80/TCPFull complete!]
[2026-06-18T09:25:59.198] [INFO] - [Using LAYER 184 for initial connect]
Please enter your number: +380**********
[2026-06-18T09:26:06.298] [INFO] - [Phone migrated to 2]
[2026-06-18T09:26:06.385] [INFO] - [Reconnecting to new data center 2]
[2026-06-18T09:26:06.455] [WARN] - [Disconnecting...]
[2026-06-18T09:26:06.455] [INFO] - [Disconnecting from 149.154.167.91:80/TCPFull...]
[2026-06-18T09:26:06.455] [INFO] - [Connecting to 149.154.167.41:80/TCPFull...]
[2026-06-18T09:26:06.456] [INFO] - [connection closed]
[2026-06-18T09:26:08.218] [INFO] - [Connection to 149.154.167.41:80/TCPFull complete!]
[2026-06-18T09:26:08.218] [INFO] - [Using LAYER 184 for initial connect]
Please enter the code you received: 

[Huakas]

I thought i was the only one having this issue and it was my fault. So yes, i have the exact same issue, and no solution sadly. Hopefully someone can help...

[d-kobzar]

@Huakas I can say that it happened all of a sudden, like Telegram changed their policies or API. But this lib was update too far ago from now ... And the most interesting fact that no one alarms about it ...
So what are you going to do with that ?

[Huakas]

@d-kobzar so i ended up trying both teleproto (which is an actively maintained fork of gramjs) and telethon (which is what both gramjs and teleproto are based on) and none of these worked for me. Maybe we are shadow banned? But creating new account and new api id and api hash didn't change anything for me.

What i ended up doing is using qr code to login. Do not ask me why THAT works but in-app code still doesn't. Here is the code for that (warning: renderQr() is ai slop):

import { TelegramClient, Api } from "teleproto";
import { StringSession } from "teleproto/sessions";
import { createInterface } from "node:readline/promises";
import qrcode from 'qrcode-terminal';

async function test_telegram() {
  const rl = createInterface({ input: process.stdin, output: process.stdout });

  const apiId = yourId;
  const apiHash = "yourHash";
  const session = new StringSession("");

  const client = new TelegramClient(session, apiId, apiHash, {
    connectionRetries: 5,
  });

  await client.connect();

  function renderQr(code: any) {
    function toBase64Url(buffer: Buffer) {
      return buffer
        .toString("base64")
        .replace(/\+/g, "-")
        .replace(/\//g, "_")
        .replace(/=+$/, "");
    }
    const encoded = toBase64Url(code.token);
    const url = `tg://login?token=${encoded}`;
    qrcode.generate(url, { small: true });
  }

  await client.signInUserWithQrCode({ apiId, apiHash }, {
    qrCode: async (code) => renderQr(code),
    onError: async (err) => { console.error(err); return true; },
  });

  console.log(await client.getMe());
  console.log("Session string:", client.session.save());

  await client.sendMessage("me", { message: "hello from teleproto" });

  rl.close();
}

test_telegram();

Just a quick heads up: as you can see i am using teleproto, but this should work exactly the same for gramjs, i am just too lazy to install gramjs again.

[d-kobzar]

@Huakas So QR code works ?

[Huakas]

@d-kobzar for me yes

[d-kobzar]

@d-kobzar for me yes

I tried, it works via Gramjs as well. I think that this happened in accordance with some new TG policy related to anty-spam protection. So users cannot farm accounts via codes. Idk why and is that fact or just my thoughts, but it's weird.

Anyway, thank you for cooperation, appreciate 👍