# Telegram Trigger — "Bad Request: bad webhook: An HTTPS URL must be provided for webhook" **URL:** \ **Category:** Questions\ **Created:** [October 27, 2025, 8:19am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165 "2025-10-27T08:19:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![matsyui](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/matsyui/32/132647_2.png) [@matsyui](https://community.n8n.io/u/matsyui)\ **Post date:** [October 27, 2025, 8:19am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/1 "2025-10-27T08:19:33Z")
I’m currently trying to set up a **Telegram Trigger** node in n8n, but I keep getting this error: ```auto Problem running workflow Bad request - please check your parameters Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook ``` Here’s my setup: - Trigger on: `Message` - No additional fields added - Hosted via **Coolify** with a **Cloudflare Tunnel** (no direct public IP, just a tunnel exposing n8n via HTTPS) ([Check the docs setup](https://coolify.io/docs/knowledge-base/cloudflare/tunnels/all-resource)) Whenever I click **Execute Node** , it fails instantly with that webhook error. Here’s a screenshot of my setup for context: ![image](https://europe1.discourse-cdn.com/n8n/original/3X/5/4/540ff647bc31661472f0f2b04e859aaeb6190dd0.png) Does Telegram reject webhook URLs when they’re behind a Cloudflare Tunnel, or is there something else I need to configure in n8n or Cloudflare for the webhook to register properly? If so, what’s the recommended setup for using the Telegram Trigger node when n8n is self-hosted in Coolify behind a tunnel? Thanks in advance ---
**Author:** ![Parintele\_Damaskin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/parintele_damaskin/32/139243_2.png) [@Parintele\_Damaskin](https://community.n8n.io/u/Parintele_Damaskin)\ **Post date:** [October 27, 2025, 8:31am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/2 "2025-10-27T08:31:13Z")
Follow this steps, and it should be OK. -Set up your Cloudflare Tunnel and get the public HTTPS URL. -Set WEBHOOK\_URL in n8n to this URL. -(If behind a reverse proxy) Set N8N\_PROXY\_HOPS=1. -Restart your n8n instance after changing environment variables. ---
**Author:** ![matsyui](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/matsyui/32/132647_2.png) [@matsyui](https://community.n8n.io/u/matsyui)\ **Post date:** [October 27, 2025, 8:42am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/3 "2025-10-27T08:42:29Z")
![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/8/28e586604d9b5e82f67cf01cf8f00dc469142e48.png) then N8N\_PROXY\_HOPS is already set to 1 WEBHOOK\_URL is already set manually and now https. i cant change the SERVICE\_URL\_N8N to https since it will cause multiple redirect since https is handled by cloudflare. after that i have restarted both server coolify proxy and n8n instance Error still showing same message Additional thing i guess: ![image](https://europe1.discourse-cdn.com/n8n/original/3X/b/b/bbebf2d5c347677a4c65e1c7483985aa72a1a00b.png) so i change the webhook to https in env, and restarted the n8n instance.. i deleted the old trigger and added a new one but still the webhook url didnt change the http to https ---
**Author:** ![Parintele\_Damaskin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/parintele_damaskin/32/139243_2.png) [@Parintele\_Damaskin](https://community.n8n.io/u/Parintele_Damaskin)\ **Post date:** [October 27, 2025, 8:51am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/4 "2025-10-27T08:51:14Z")
check what webhook URL is currently registered with Telegram here by replacing placeholder for bot token: [https://api.telegram.org/botYOUR\_TOKEN/getWebhookInfo](https://api.telegram.org/botYOUR_TOKEN/getWebhookInfo) If it’s not your public HTTPS tunnel URL, n8n is not registering it correctly. Or Cloudflare’s proxy/firewall settings can block Telegram’s webhook requests. If you are using Cloudflare’s proxy (orange cloud), try switching to DNS-only (grey cloud) or review your Cloudflare firewall rules to ensure Telegram’s requests are not being blocked … ---
**Author:** ![matsyui](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/matsyui/32/132647_2.png) [@matsyui](https://community.n8n.io/u/matsyui)\ **Post date:** [October 27, 2025, 9:01am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/5 "2025-10-27T09:01:24Z")
> [@Parintele\_Damaskin](#): > > Cloudflare’s proxy/firewall settings can block Telegram’s webhook requests. If you are using Respond from: [https://api.telegram.org/botYOUR\_TOKEN/getWebhookInfo](https://api.telegram.org/botYOUR_TOKEN/getWebhookInfo) ```auto {"ok":false,"error_code":404,"description":"Not Found"} ``` Cloudflare’s proxy/firewall settings can block Telegram’s webhook requests. If you are using - No firewall Cloudflare’s proxy (orange cloud), try switching to DNS-only (grey cloud) or review your Cloudflare - tried still same firewall rules to ensure Telegram’s requests are not being blocked - no setup rules I have generated this token from what i’ve followed on youtube, I chat and create a bot got the token from BotFather ![image](https://europe1.discourse-cdn.com/n8n/original/3X/5/1/5187ac471bf6b352c05e0219c875bdbf85e042db.png) ---
**Author:** ![matsyui](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/matsyui/32/132647_2.png) [@matsyui](https://community.n8n.io/u/matsyui)\ **Post date:** [October 27, 2025, 9:28am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/6 "2025-10-27T09:28:37Z")
what i did now is i backup everything and recreate an instance of n8n entirely before deploying what i did is updatte the compose file and env with the https for the webhook setup n8n and import everything and walaa!!! it works.. lol ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/2/f27af9269d38cd472d1735cd5f96ddced7d1be85.png) i will mark it as the solution. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/36532_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [November 3, 2025, 9:28am UTC](https://community.n8n.io/t/telegram-trigger-bad-request-bad-webhook-an-https-url-must-be-provided-for-webhook/212165/7 "2025-11-03T09:28:57Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.