422 Unprocessable Entity


  • Used Zammad version: -3.4.x
  • Used Zammad installation source: (source, package, …) Centos 7 with Zammad installation procedures
  • Operating system: Centos 7
  • Browser + version: Firefox v79 - 64bit, also tries Chrome and Safari, latest releases

Expected behavior:

  • When the Telegram bot is created on Botfather, and the token is inserted in the Zammad Telegram configuration, the light goes green. When sending a message from Telegram, it gets the correct Welcome Message from the Zammad configuration, but the Telegram messages are not coming through to Zammad.

I am using a Letsencrypt Certificate.

Actual behavior:

  • Hi there,

I am running Zammad 3.4.x completely standard on Centos 7, as per the installation instructions. When I send the messages from Telegram, the message is not showing in Zammad, and in the Production log shows the following:

Completed 422 Unprocessable Entity in 79ms

I am using a Letencrypt certificate, and the output from https://api.telegram.org/bot<my ctoken/getWebhookInfo is as follows:

{“ok”:true,“result”:{“url”:“https://support.dfacto.one/api/v1/channels_telegram_webhook/YhlJbF7rGSX9Iw?bid=1338852667",“has_custom_certificate”:false,“pending_update_count”:13,“last_error_date”:1594820476,“last_error_message”:"Wrong response from the webhook: 422 Unprocessable Entity”,“max_connections”:40}}

Please assist, as the Telegram channel is critical to the deployment.


Steps to reproduce the behavior:

Please provide the production log of the moment you’re trying to send the message via telegram.
Note that the full traceback is required - other wise we’re fishing in the dark as there may be tons of reasons.