starred/twofactor_gateway-nextcloud

Fork 0

mirror of https://github.com/nextcloud/twofactor_gateway.git synced 2026-04-25 09:05:55 +03:00

[GH-ISSUE #398] Telegram bot not answering #86

New issue

Closed

opened 2026-02-26 05:33:00 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 05:33:00 +03:00

Owner

Originally created by @strites on GitHub (Nov 23, 2020).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/398

I am having problems with telegram 2fa

I created the bot, configured it in next loud, started a conversation with the bot (probably I had a conversation already open with it) but bot is not answering.
Every message I send get read immediately, but the bot is mute.

What can I do?
Is there a way to debug this? Nextcloud's logs are void of anything telegram like....

Originally created by @strites on GitHub (Nov 23, 2020). Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/398 Hi I am having problems with telegram 2fa I created the bot, configured it in next loud, started a conversation with the bot (probably I had a conversation already open with it) but bot is not answering. Every message I send get read immediately, but the bot is mute. What can I do? Is there a way to debug this? Nextcloud's logs are void of anything telegram like....

kerem closed this issue

2026-02-26 05:33:00 +03:00

kerem commented

2026-02-26 05:33:01 +03:00

Author

Owner

@j-ed commented on GitHub (Nov 23, 2020):

This is the issue and feature request tracker for the developers and not the Nextcloud help forum. If you have any question to the software or how it need to be configured, you should address it there first 😉

The whole set-up process has been described on the admin documentation of the app:

https://nextcloud-twofactor-gateway.readthedocs.io/en/latest/Admin%20Documentation/

@j-ed commented on GitHub (Nov 23, 2020): This is the issue and feature request tracker for the developers and not the Nextcloud [**help forum**](https://help.nextcloud.com/). If you have any question to the software or how it need to be configured, you should address it [**there**](https://help.nextcloud.com/) first 😉 The whole set-up process has been described on the admin documentation of the app: https://nextcloud-twofactor-gateway.readthedocs.io/en/latest/Admin%20Documentation/

kerem commented

2026-02-26 05:33:01 +03:00

Author

Owner

@strites commented on GitHub (Nov 23, 2020):

Yes, I followed it.
I got the bot created, got the API key and pasted it when "occ twofactorauth:gateway:configure telegram" asked it.

I just tried with a new bot.
When I start the chat with the bot, nothing returns.

@strites commented on GitHub (Nov 23, 2020): Yes, I followed it. I got the bot created, got the API key and pasted it when "occ twofactorauth:gateway:configure telegram" asked it. I just tried with a new bot. When I start the chat with the bot, nothing returns.

kerem commented

2026-02-26 05:33:01 +03:00

Author

Owner

@j-ed commented on GitHub (Nov 23, 2020):

So you mean, that you've successfully finished step 1 and requested/received your own Telegram ID as described in the user documentation of the app? - ups, the numbering has been screwed-up -

Next you've followed step 1 - 3 of the user documentation and contacted your newly created bot and have send e,g. "Hello" to this bot without getting a reply? That's absolutely ok, because it isn't written that you should expect a reply here and makes sure that the bot knows your online. Jump to step 4 and continue the configuration process as usual.

@j-ed commented on GitHub (Nov 23, 2020): So you mean, that you've successfully finished **step 1** and requested/received your own Telegram ID as described in the [user documentation](https://nextcloud-twofactor-gateway.readthedocs.io/en/latest/User%20Documentation/) of the app? **- ups, the numbering has been screwed-up -** Next you've followed **step 1 - 3** of the user documentation and contacted your newly created bot and have send e,g. "Hello" to this bot without getting a reply? That's absolutely ok, because it isn't written that you should expect a reply here and makes sure that the bot knows your online. Jump to **step 4** and continue the configuration process as usual.

kerem commented

2026-02-26 05:33:01 +03:00

Author

Owner

@strites commented on GitHub (Nov 23, 2020):

Documentation:
Open your Telegram client, search for @my_id_bot and start a conversation.

In reply @my_id_bot provides your personal id to you, e.g. 998877665.

Reality:
I open telegram, start a conversation with my bot
My bot doesn't tell me anything, so I don't get the "personal ID" I should paste in the config page when activating the 2fa

@strites commented on GitHub (Nov 23, 2020): Documentation: Open your Telegram client, search for @my_id_bot and start a conversation. In reply @my_id_bot provides your personal id to you, e.g. 998877665. Reality: I open telegram, start a conversation with my bot My bot doesn't tell me anything, so I don't get the "personal ID" I should paste in the config page when activating the 2fa

kerem commented

2026-02-26 05:33:01 +03:00

Author

Owner

@j-ed commented on GitHub (Nov 23, 2020):

Ok, so we slowly narrowing down the problem. You haven't any problems getting a reply from the newly set-up bot, because you haven't reached this configuration step yet, but you're not getting a reply from the ID Bot?! Please try to contact the @Get My ID bot instead of the @my_id_bot to get your personal ID. Once you've received your ID continue with the setup process as described in the documentation.

@j-ed commented on GitHub (Nov 23, 2020): Ok, so we slowly narrowing down the problem. You haven't any problems getting a reply from the newly set-up bot, because you haven't reached this configuration step yet, but you're not getting a reply from the ID Bot?! Please try to contact the **`@Get My ID`** bot instead of the `@my_id_bot` to get your personal ID. Once you've received your ID continue with the setup process as described in the documentation.

kerem commented

2026-02-26 05:33:02 +03:00

Author

Owner

@strites commented on GitHub (Nov 23, 2020):

Oh... Found the problem... I was trying to get the ID from the bot I created (that is referenced in the doc as @my_nc_bot ) while I had to literally search for a bot called @my_id_bot

@strites commented on GitHub (Nov 23, 2020): Oh... Found the problem... I was trying to get the ID from the bot I created (that is referenced in the doc as @my_nc_bot ) while I had to literally search for a bot called @my_id_bot

kerem commented

2026-02-26 05:33:02 +03:00

Author

Owner

@nekkitl commented on GitHub (Aug 20, 2023):

Use one more bot to get ID - that's NOT a deal. Maybe somebody knows how throw answer after /start by user?

@nekkitl commented on GitHub (Aug 20, 2023): Use one more bot to get ID - that's **NOT** a deal. Maybe somebody knows how throw answer after `/start` by user?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/twofactor_gateway-nextcloud#86

No description provided.

Rows
Columns