7 days ago
I’m contacting you because my Telegram bot and admin website have stopped working, and I need help identifying the cause.
On October 14, my workspace on mail- [email protected] was banned because my plan used a Lenny’s Product Pass discount code. I later received your email confirming that the ban was lifted because the enforcement had been too broad.
Thank you for correcting the mistake and adding $20 in credit to my account.
However, since the ban and subsequent unbanning, I’m experiencing issues with my hosted services:
-
My Telegram bot does not respond when I send the /start command even after i have redeployed the project and its showing active on railway.
-
My admin website returns a 502 Application failed to respond error.
-
My Railway workspace shows an active Hobby plan, and the latest deployment is marked as successful, but the services are still not working as expected.
I previously found an application error in the logs, but given that my workspace was banned and my services were stopped, I’d appreciate your help determining whether any platform-side restrictions or deployment issues remain.
Could you please check whether my workspace and services have been fully restored following the reversal of the ban? If any additional action is required on my side, please let me know.
My project is - ingenious-appreciation > splendid-analysis
I’m happy to provide the project names, service names, deployment IDs, and relevant logs if needed.
Thank you for your time and assistance.
Best regard
3 Replies
7 days ago
This thread has been marked as private.
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
The earlier restriction on your workspace has been lifted, and nothing on our side is currently blocking your services from running.
In ingenious-appreciation, splendid-analysis (the service with your Telegram token and the public domain) has a Cron Schedule of 0 0 * * * set in its settings. A cron service only starts once a day at 00:00 UTC and is meant to run a task and exit, so it does not suit a long-running web server or Telegram bot and explains both the bot not answering /start and the 502 on that domain. Clearing the Cron Schedule in the service's settings and redeploying will run it continuously. See Cron Jobs.
The hemloo-bot service in that same project has no environment variables (including no TELEGRAM_BOT_TOKEN) and no public domain, so it cannot serve the bot or the admin site in its current state.
Status changed to Awaiting User Response Railway • 7 days ago
an hour ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 hour ago
Railway
The earlier restriction on your workspace has been lifted, and nothing on our side is currently blocking your services from running. In ingenious-appreciation, splendid-analysis (the service with your Telegram token and the public domain) has a Cron Schedule of `0 0 * * *` set in its settings. A cron service only starts once a day at 00:00 UTC and is meant to run a task and exit, so it does not suit a long-running web server or Telegram bot and explains both the bot not answering /start and the 502 on that domain. Clearing the Cron Schedule in the service's settings and redeploying will run it continuously. See [Cron Jobs](https://docs.railway.com/cron-jobs). The hemloo-bot service in that same project has no environment variables (including no `TELEGRAM_BOT_TOKEN`) and no public domain, so it cannot serve the bot or the admin site in its current state.
an hour ago
i have now updated cron setting and removed it and the admin panel web started working. But my hemloo-bot is not working and repying even i have already added variable to ut. Kindly help
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.
This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • about 1 hour ago
an hour ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 hour ago