Telegram bot deploy fails with secret TOKEN not found and wrong bot behavior
nekitnalogin-glitch
FREEOP

3 hours ago

Problem:

I deploy a Python Telegram bot on Railway from GitHub. It worked earlier, then builds started failing with secret TOKEN not found. After changing variables and code, a different bot requiring subscription to A_ToolsX responds instead of mine. I created a new bot and new project, but it still fails. I need help with correct TOKEN setup and a clean deployment.

Resources:

Old project: precious-generosity, production, service my-courier-bot, repo nekitologin-glitch/my-courier-bot.

Failing deployment: 2026-10-04 ~21:31 MSK.

Last success: 2026-10-04 ~18:49 MSK.

New project/repo: [courier-bot-v2]

New service/deployment: [URL/ID]

Error:

text

install mise packages: python

secret TOKEN not found

Attempts:

Removed TOKEN variable.

Hardcoded token in code — same error.

Re-added TOKEN without trailing space, value from BotFather. After redeploy, bot came online but required subscription to A_ToolsX, not in my code.

Deleted old main.py, uploaded clean code — no change.

Created new bot and repo, but still not working.

Please check service configuration, variables, and build logs: why TOKEN is not found and why the deployed bot uses a token/channel not present in my code. Do not delete resources without my consent; I need diagnosis.

Prepared with Railway's support template (v1).

$10 Bounty

0 Replies

Railway
BOT

3 hours ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 3 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...