I’m having trouble with my Telegram bot webhook setup. When I configured the webhook URL, everything appeared to work correctly at first. However, my bot doesn’t respond to messages anymore.
I tested my webhook handler code using the getUpdates method and it works perfectly fine. My server has a valid SSL certificate installed. But when I call getWebhookInfo, I get this error message: “Wrong response from the webhook: 410 Gone”.
Has anyone encountered this 410 Gone response before? What could be causing this issue with my webhook endpoint?
yep, a 410 means your webhook isn’t pointing to a live resource. double check the url you set and ensure your endpoint is up. if you made any changes, they need to be reflected in your config or the handler might not be processing right.
This error bit me hard - spent hours debugging only to find my web server was returning 410 for endpoints that weren’t registered in the app routes. Here’s the tricky part: 410 Gone means the resource existed before but now it’s permanently removed. So your webhook URL probably worked initially, then something changed server-side. Check if your framework is still serving that exact path and make sure the HTTP method is POST. Deployments or server restarts can reset route configs. Also check your server logs - are the webhook requests even reaching your app, or is the web server rejecting them before they hit your bot code?
Had the exact same problem when I moved my webhook to a different path but forgot to update the URL with Telegram. The 410 Gone error means the resource used to exist but isn’t there anymore. Check if your server routing changed or if middleware is blocking the webhook path. Make sure your endpoint is actually getting POST requests from Telegram’s IP ranges - sometimes firewall rules or server configs mess this up. Try deleting the current webhook with deleteWebhook and set it up again with the right URL.