Https (webhook-)urls for self-hosted-starter-kit

[Ingo]

Describe the problem/error/question

Using the self-hosted-ai-starter-kit, I encountered a problem with the Telegram Trigger node. As far as I understand, the Telegram API requires the webhook URL to use a HTTPS address but the self-hosted-ai-starter-kit is not configured that way (not out of the box, at least). My webhook urls currently look like this: “**http://**localhost:5678/webhook-test/…/webhook”.

I am looking for a pragmatic approach to adjust that. I wasn’t successful finding any documentation about this specific setup.

What is the error message (if any)?

Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook

400 - {“ok”:false,“error_code”:400,“description”:“Bad Request: bad webhook: An HTTPS URL must be provided for webhook”}

Information on your n8n setup

• n8n version: 1.68.0 (self-hosted-ai-starter-kit)
• Running n8n via: Docker
• Operating system: Windows 10

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Ingo]

Ok, interesting, I found something in the n8n documentation in the hosting context: n8n with tunnel

To be able to use webhooks for trigger nodes of external services like GitHub, n8n has to be reachable from the web. n8n has a tunnel service which redirects requests from n8n’s servers to your local n8n instance.

If I am not mistaken, this sounds like (part of) the solution I am asking for. Would this also solve the https aspect of it?!

[Jon]

Hey @Ingo,

I would use ngrok or Cloudflared as a tunnel option as it would be quicker, The other option would be to follow the normal documentation and configure a reverse proxy to handle the connection.