Can a telegram trigger not respond because of an SSL certificate?

Describe the problem/error/question

I created a new workflow and added a telegram trigger and successfully connected a new bot to it that had never been used anywhere before.

I started the bot with the /start command, but the trigger does not respond to the command in any way.

I have done this several times, but there is no response.

I don’t have an SSL network certificate installed on the server right now.

Common Name (CN) TRAEFIK DEFAULT CERT
Organisation (O)
Organisation (OU)

Could this be affecting the telegram trigger not working?

Information on your n8n setup

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

It may be that the Telegram can’t access your bot webhook. Make sure the url in the Webhooks URLs section are available from the internet.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.