-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telegram Client Hangs Up on Connect #691
Comments
having similar issue, the only thing that differs that I initialize it a bit differently const session = new StringSession(account.session)
const tgClient = new TelegramClient(session, account.api_id, account.api_hash, {
connectionRetries: 5,
floodSleepThreshold: 0,
useWSS: true,
testServers: false,
})
tgClient.setLogLevel(LogLevel.DEBUG)
await tgClient.connect() and got this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been trying to connect to telegram using TelegramClient in a worker thread. The worker hangs up at
await client.connect
and after retries throws connection error. Strange that it works locally but is a problem with Docker.The application has been dockerized. Here is the docker-compose.yml.
DockerFile
Finally, caddyfile for reverse proxy
Any ideas?
Some observations:
I have checked Docker network and the containers are all connected and I could ping redis and caddy from within the telegram.
Changing to
connectionRetries: -1
yields the result false on connect instead of hanging up. So, it doesn't connect and timeout.The text was updated successfully, but these errors were encountered: