starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #3700] [BUG] Broken Telegram alert #2448

New issue

Closed

opened 2026-02-27 03:03:00 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 03:03:00 +03:00

Owner

Originally created by @Nord1cWarr1or on GitHub (Dec 6, 2021).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3700

Originally assigned to: @johnoclockdk on GitHub.

User Story

As a LGSM user, I want send test alert on telegram, but it doesn't happen

Basic info

Distro: Debian 11
Game: Counter-Strike 1.6
Command: test-alert
LinuxGSM version: v21.4.1

Further Information

Commit github.com/GameServerManagers/LinuxGSM@44daf20083 (last commit at file alert_telegram.sh) broke Telegram alert.
I tried to send test-alert, but get an error:

[ .... ] Sending Alert csserver: Sending Telegram alertparse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 4, column 431
[ FAIL ] Sending Alert csserver: Sending Telegram alert: {"ok":false,"error_code":400,"description":"Bad Request: message text is empty"}

Then I copied code from previous commit (github.com/GameServerManagers/LinuxGSM@48308ec61e) at this file and everithing worked as expected.

[  OK  ] Sending Alert csserver: Sending Telegram alert

To Reproduce

Steps to reproduce the behaviour:

Configure telegram alerts in lgsm config
Send test-alert
See error

Expected behaviour

[  OK  ] Sending Alert csserver: Sending Telegram alert

Originally created by @Nord1cWarr1or on GitHub (Dec 6, 2021). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3700 Originally assigned to: @johnoclockdk on GitHub. ## User Story As a LGSM user, I want send test alert on telegram, but it doesn't happen ## Basic info * **Distro:** Debian 11 * **Game:** Counter-Strike 1.6 * **Command:** test-alert * **LinuxGSM version:** v21.4.1 ## Further Information Commit https://github.com/GameServerManagers/LinuxGSM/commit/44daf200834c5bf56956531ff082dc1045021253 (last commit at file `alert_telegram.sh`) broke Telegram alert. I tried to send test-alert, but get an error: ``` [ .... ] Sending Alert csserver: Sending Telegram alertparse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 4, column 431 [ FAIL ] Sending Alert csserver: Sending Telegram alert: {"ok":false,"error_code":400,"description":"Bad Request: message text is empty"} ``` Then I copied code from previous commit (https://github.com/GameServerManagers/LinuxGSM/commit/48308ec61e6f01e83e7e127a8b25c8fda4ef1355) at this file and everithing worked as expected. ``` [ OK ] Sending Alert csserver: Sending Telegram alert ``` ## To Reproduce Steps to reproduce the behaviour: 1. Configure telegram alerts in lgsm config 2. Send test-alert 3. See error ## Expected behaviour ``` [ OK ] Sending Alert csserver: Sending Telegram alert ```

kerem

2026-02-27 03:03:00 +03:00

closed this issue
added the
distro: Debian

info: alerts

command: send
labels

kerem commented

2026-02-27 03:03:01 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 6, 2021):

Potential duplicates:

[#3567] [BUG] Broken server version (63.39%)

@github-actions[bot] commented on GitHub (Dec 6, 2021): Potential duplicates: - [#3567] [BUG] Broken server version (63.39%)

kerem commented

2026-02-27 03:03:01 +03:00

Author

Owner

@johnoclockdk commented on GitHub (Dec 6, 2021):

i know this bug but from a other game #3463

@johnoclockdk commented on GitHub (Dec 6, 2021): i know this bug but from a other game #3463

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@johnoclockdk commented on GitHub (Dec 6, 2021):

@Nord1cWarr1or do you have any color code in alert

@johnoclockdk commented on GitHub (Dec 6, 2021): @Nord1cWarr1or do you have any color code in alert

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@Nord1cWarr1or commented on GitHub (Dec 6, 2021):

@Nord1cWarr1or do you have any color code in alert

Sorry, but what do you mean by color code? And where it shoud be?

@Nord1cWarr1or commented on GitHub (Dec 6, 2021): > @Nord1cWarr1or do you have any color code in alert Sorry, but what do you mean by color code? And where it shoud be?

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@Nord1cWarr1or commented on GitHub (May 30, 2022):

Any news? @johnoclockdk @dgibbs64

@Nord1cWarr1or commented on GitHub (May 30, 2022): Any news? @johnoclockdk @dgibbs64

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@bosmadev commented on GitHub (Feb 2, 2023):

I seem to experience the same issue.

When running this code directly, there is no issue.
curl -s -X POST https://api.telegram.org/bot5865808094:ASl_UM/sendMessage -F chat_id='-1001804566104' -F text='test message'

Reading furthermore in forums, all files are EOL encoded for UNIX, no hidden characters found.

Another supporter from discord with their latest LGSM is able to send a test alert with the same details in common.cfg

@bosmadev commented on GitHub (Feb 2, 2023): I seem to experience the same issue. When running this code directly, there is no issue. `curl -s -X POST https://api.telegram.org/bot5865808094:ASl_UM/sendMessage -F chat_id='-1001804566104' -F text='test message'` Reading furthermore in forums, all files are EOL encoded for UNIX, no hidden characters found. Another supporter from discord with their latest LGSM is able to send a test alert with the same details in common.cfg

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 20, 2023):

Just completed a refactor of alerts and did not spot any issues. Closing

@dgibbs64 commented on GitHub (Oct 20, 2023): Just completed a refactor of alerts and did not spot any issues. Closing

kerem commented

2026-02-27 03:03:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 21, 2024):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Oct 21, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.