Telegram Trigger on Docker Localhost: Bad Request / HTTPS Webhook Error

Questions
1

Hi everyone,

I’m running n8n via Docker on my local machine using localhost:5678. When I try to use the Telegram Trigger, I encounter the following issues:

  1. When executing the workflow:
Bad request - please check your parameters
  1. When activating the workflow:
Bad Request: bad webhook: An HTTPS URL must be provided for webhook

I understand that Telegram requires a public HTTPS URL for webhooks, but I’m running n8n locally via Docker. Could someone advise on the best way to make Telegram Trigger work in a local Docker setup?

Thanks in advance!

2

In order to register a webhook, Telegram requires the webhook to be HTTPS instead of HTTP. You can use this to get yourself started:

3

Hey @yunus_emre1 , if you can share the ss of the telegram node and json payload if any, also use ngrok for webhook triggers as it will not work with local host

4

yes exactly what i said

5

I have a question. in this video (5:14) , He added host path(n8n-data) but I can’t see my n8n-data file.
Do I need to create new file ?

6

The reason they have it and you don’t is the difference in the initial configuration. They had their bind mount configured to store n8n_data in the home folder, while yours is probably somewhere else.