"Unable to send entry to Telegram"

[silaxe]

Since a few weeks, my Telegram integration has stopped working. Meanwhile I started to receive the following error in my log: "Unable to send entry to Telegram".

Could you give me any direction where this error might come from?

Many thanks in advance.

[fguillot]

It's coming from here:

v2/internal/integration/integration.go

Lines 625 to 630 in 13986e9

	slog.Error("Unable to send entry to Telegram",
	slog.Int64("user_id", userIntegrations.UserID),
	slog.Int64("entry_id", entry.ID),
	slog.String("entry_url", entry.URL),
	slog.Any("error", err),
	)

You should have the error details in the logs.

[silaxe]

Thanks! I have set the LOG_LEVEL to debug and will check the output.

[silaxe]

This is the log I have around the Telegram error:

jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Feed icon already exists" feed_id=21
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Feed icon already exists" feed_id=7
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Feed modified" user_id=2 feed_id=27 etag_header="" last_modified_header=""
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Request response" effective_url=https://environment.ec.europa.eu/node/92/rss_en content_length=6708 content_encoding=gzip content_type="application/rss+xml; charset=utf-8"
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Updated next check date" user_id=2 feed_id=27 feed_url=https://environment.ec.europa.eu/node/92/rss_en feed_ttl_minutes=0 cache_control_max_age_in_minutes=5 expires_in_minutes=-245>
jui 28 17:42:21 NESTOR miniflux[3868324]: level=ERROR msg="Unable to send entry to Telegram" user_id=2 entry_id=160 entry_url=https://www.lefigaro.fr/flash-eco/droits-de-douane-l-industrie-automobile-europeenne-entre-soulagement-et-crainte>
jui 28 17:42:21 NESTOR miniflux[3868324]: level=ERROR msg="Unable to send entry to Telegram" user_id=2 entry_id=161 entry_url=https://decrypt.co/332074/paypal-enable-retailers-accept-bitcoin-other-cryptocurrencies error="telegram: unable t>
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Feed icon already exists" feed_id=11
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Feed modified" user_id=2 feed_id=24 etag_header="\"70a6e493a8a862eda721ecb3e93eeb41-gzip\"" last_modified_header="Mon, 28 Jul 2025 13:33:50 GMT"
jui 28 17:42:21 NESTOR miniflux[3868324]: level=DEBUG msg="Request response" effective_url="https://www.euractiv.com/?feed=mcfeed" content_length=18645 content_encoding=gzip content_type="text/xml; charset=UTF-8"

I still fail to see what triggers the error. Any hint?

Thanks!

[fguillot]

Your log messages are truncated somehow. The real error is at the end of the line: error="telegram: unable t>. It could be any error from this file: https://github.com/miniflux/v2/blob/main/internal/integration/telegrambot/client.go

You can also double check your settings: bot token and chat ID

[silaxe]

Thanks for your help, indeed I did not see the truncated part of the error!

Somehow my BASE_URL was reverted back to the default http://localhost, hence the thrown error.

[toketin]

Hi, have you been able to fix this issue? I'm experiencing same issue with last Miniflux version 2.2.13, because it's not able to send any message to my telegram bot. The bot token and chat ID are right and they are correctly working with another tool.

[silaxe]

Yes, I changed the BASE_URL to the external URL of my miniflux server.

[toketin]

Ok tkank you. Sorry if I ask it, but in which config file have you changed this? I'm using the docker container version, and I haven't any volume with its config file.