'
```
How can I fix this error ?
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [November 1, 2019, 9:28am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/122 "2019-11-01T09:28:17Z")
Can you share what you see in the `info` tab of the log? Looks like that’s just the backtrace
---
### Author:  [@Surendra-Patil](https://meta.discourse.org/u/Surendra-Patil)
#### Post date: [November 1, 2019, 9:30am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/123 "2019-11-01T09:30:29Z")
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [November 1, 2019, 9:42am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/124 "2019-11-01T09:42:33Z")
It looks like your server is having trouble contacting [https://api.telegram.org](https://api.telegram.org). Are you using a [supported installation](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)? Is your server inside a network which could be interfering with outgoing requests?
---
### Author:  [@Surendra-Patil](https://meta.discourse.org/u/Surendra-Patil)
#### Post date: [November 4, 2019, 8:45am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/125 "2019-11-04T08:45:41Z")
Hi @david , sorry for late reply.
Yes the site is accessible (redirects to [Bots: An introduction for developers](https://core.telegram.org/bots) ).
Also getting this below error.
```plaintext
ActionView::MissingTemplate (Missing template discourse_telegram_notifications/telegram/hook, application/hook with {:locale=>[:en_US, :en], :formats=>[:html], :variants=>[], :handlers=>[:raw, :erb, :html, :builder, :ruby]}. Searched in:
* "/var/www/discourse/app/views"
* "/var/www/discourse/plugins/docker_manager/app/views"
)
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionview-6.0.0/lib/action_view/path_set.rb:48:in `find'
```
On running `openssl s_client -connect api.telegram.org:443` got below result.
```plaintext
CONNECTED(00000003)
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 308 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
```
@codinghorror Recently openssl version was changed in latest discourse docker container due to which this issue is arising. On host machine I tried using OpenSSL 1.1.1 for telegram api and it loads the certificate.
---
### Author:  [@Flashio](https://meta.discourse.org/u/Flashio)
#### Post date: [December 1, 2019, 8:32pm UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/126 "2019-12-01T20:32:20Z")
@david
New bug: after changing topic’s tag the first message of that topic will be send to telegram as a notification. So every time you change a topic’s tag there will be a notification in telegram.
**NOTE:** The bug is active on 2.4.0.beta7 ([06c2e28bbb](https://github.com/discourse/discourse/commits/06c2e28bbb76a6bba94717d87ac2f796e3de542b)). To activate the bug topic starter must create topic with tags, after that he must reply to that thread and topic starter’s message must be last in the topic. After that if topic starter will change the tag, then plugin will send notification which will include first post’s text.
**So how to receive infinite notification with first message of the topic:**
1. Topic Starter must create a topic
2. Topic Starter must reply to this topic
3. Topic Starter must change the topic’s tag. And now every time he change the topic’s tag everyone who subscribed to this topic will receive a notification that will include first message of that topic.
If someone will reply after topic starter’s reply and topic starter will change the topic’s tag: then notification with first message will still arrive, but only once.
Please, fix that issue as I’m using Discourse as a notification platform. 🙂
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [December 2, 2019, 2:04pm UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/127 "2019-12-02T14:04:53Z")
Do the users also receive the ‘infinite notifications’ in the Discourse user interface?
This plugin uses the same notification system as Discourse itself, so I would be surprised if this issue is specific to the telegram notifications.
---
### Author:  [@Flashio](https://meta.discourse.org/u/Flashio)
#### Post date: [December 2, 2019, 9:27pm UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/128 "2019-12-02T21:27:00Z")
> [@david](#):
>
> This plugin uses the same notification system as Discourse itself, so I would be surprised if this issue is specific to the telegram notifications.
Yes. When topic starter changes topic’s tag it shows up as a notification in Discourse. (only if topic starter is the last one who replied to this topic).
Can I disable it somehow or this is a bug? This bug/feature comes with 2.4.0.beta7 update.
By the way, after last update ([87a298a59b](https://github.com/discourse/discourse/commits/87a298a59b67df9c3a752d7506b3a9fce215fd9d)) the infinite notifications while changing topic’s tag is gone. Now it comes only with one notification when tag is changed. But still, how to disable notification when changing tag? Notification comes like “reply notification” but it is not.
This notification was received after “fiss” as topic started changed the tag.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [December 3, 2019, 12:00am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/129 "2019-12-03T00:00:57Z")
Do you have the tags set to “watching” in your user preferences?
---
### Author:  [@Flashio](https://meta.discourse.org/u/Flashio)
#### Post date: [December 3, 2019, 3:36am UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/130 "2019-12-03T03:36:31Z")
I’ve checked. No. 🙂 All of my team just set “watching” in the category, but not for tags. There was no such trouble before an update by the way.
---
### Author:  [@thaidb](https://meta.discourse.org/u/thaidb)
#### Post date: [December 24, 2019, 3:21pm UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/131 "2019-12-24T15:21:25Z")
I get this error:
> translation missing: vi.discourse\_telegram\_notifications.message.watching\_first\_post
So, i can’t get notification
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 24, 2019, 5:04pm UTC](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483/133 "2019-12-24T17:04:36Z")
The plugins isn’t translated into your language.
You can send a pull request with the translation here: [discourse-telegram-notifications/config/locales at main · davidtaylorhq/discourse-telegram-notifications · GitHub](https://github.com/davidtaylorhq/discourse-telegram-notifications/tree/master/config/locales)
[Next page](https://meta.discourse.org/t/telegram-notifications-plugin-discourse-telegram-notifications/60483.md?page=2)