Self-hosted: Attribution signature persists despite ALL known solutions (reboot, prune, etc.)

[Arslan_Biiarslanov]

Describe the problem/error/question

I am facing a persistent issue where I cannot remove the “This message was sent automatically with n8n” signature from my Telegram bot messages, despite following all the official documentation and troubleshooting steps.

What is the error message (if any)?

There is no specific error message. The problem is that the signature “This message was sent automatically with n8n” is still added to all Telegram messages from production workflows, even though the correct environment variable is set.

Please share your workflow

(I am leaving this empty for now, as the problem is not with a specific workflow’s logic, but with the overall n8n environment configuration. The signature appears on all workflows that use the Telegram node.)

Information on your n8n setup

• n8n version: latest (the issue was also present on 1.103.2)
• Database (default: SQLite): SQLite (default)
• n8n EXECUTIONS_PROCESS setting (default: own, main): own (default)
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker (using docker-compose)
• Operating system: Linux (on a Hetzner server with Nginx as a reverse proxy)

---

Summary of Troubleshooting Steps Performed

To show that I have already tried all standard solutions, here is a detailed list of what has been done:

1. Set Environment Variable: I have correctly set N8N_DISABLE_PRODUCTION_WEBHOOK_ATTRIBUTION=true in my docker-compose.yml. I confirmed with docker inspect that the container is running with this variable.

2. Checked Nginx: My Nginx configuration is correct. sudo nginx -t shows no errors.

3. Reset Telegram Webhook: I have repeatedly used the /setWebhook API call to clear the webhook and re-registered it through the workflow. /getWebhookInfo confirmed it was cleared successfully each time.

4. Full System Restart & Update: I have updated n8n to the latest version, pruned the entire Docker system (docker system prune -a), restarted the Docker service, and even rebooted the entire server.

Despite all these steps, the signature still appears. This seems to be a very unusual bug. Could you please provide any insight or assistance?

Thank you for your help!

[King_Samuel_David]

Hey @Arslan_Biiarslanov

In the node, options you should see n8n sttribute, just disable it, it’s enabled by default

I hope this helps, please do mark as solution if fixes it many thanks
Samuel