n8n · Telegram Trigger node
Bad request: bad webhook: An HTTPS URL must be provided for webhook
Short answer
This n8n Telegram Trigger error occurs when you run n8n behind a reverse proxy and there is a problem with your instance webhook URL. Configure TLS/SSL termination in your reverse proxy.
VerifiedLast verified
01Error text
Bad request: bad webhook: An HTTPS URL must be provided for webhook02Likely causes
- n8n runs behind a reverse proxy and the
WEBHOOK_URLenvironment variable is not set to the public HTTPS URL of the instance. For Telegram, this URL must use HTTPS.
03How to fix it
- Configure TLS/SSL termination in your reverse proxy.
- Update your
WEBHOOK_URLenvironment variable to use the HTTPS address.
04Official documentation
→Related errors
- Invalid cron expressionThis n8n Schedule Trigger error occurs when Trigger Interval is set to Custom (Cron) and n8n does not understand your cron expression. Check that your cron expression follows the syntax used in the n8n cron examples.
- Only one webhook per path and methodn8n shows this message because it only permits registering one webhook for each path and HTTP method combination. Unpublish the workflow with the conflicting webhook.
- 524 timeout on n8n Cloud webhooksAn incoming webhook request on n8n Cloud fails with a 524 status code if your webhook does not respond within 100 seconds. For long-running processes, introduce polling logic with two separate webhooks.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for n8n work:Open n8n jobsn8n rates and salaries