starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #3973] [BUG] Discord alerts send invalid JSON when sending servername #2565

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Arthur-D on GitHub (Aug 30, 2022).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3973

User Story

As a server administrator, I want Discord alerts to work without hassle for everyone so that they don't give up on getting alerts.

Basic info

Distro: [Ubuntu 18.04.6]
Game: [Minecraft]
Command: [test-alert]
LinuxGSM version: [v22.1.0]

Further Information

Sending Discord alerts fails with a parse error, listed in the To Reproduce section of this bug report. I managed to work around it by changing line 21 in lgsm/functions/alert_discord.sh from
"title": "${servername}", to
"title": "Minecraft", and thus exchanging the variable for a static name.

At first I thought the "invalid escape" bit in the error message meant I couldn't have a space in my Discord server name, so I changed its name from "Multiplayer Minecraft" to just "Minecraft" and made a new webhook, just in case. But it did not resolve the issue, so I had to go with the above workaround instead.

To Reproduce

Steps to reproduce the behaviour:

In my instance config lgsm/config-lgsm/mcserver/mcserver.cfg I added the Notification Alerts section from the template lgsm/config-lgsm/mcserver/_default.cfg
I followed https://docs.linuxgsm.com/alerts/discord but added the URL to my instance mcserver.cfg instead of common.cfg
I ran ./mcserver test-alert
See error:
[ .... ] Sending Alert mcserver: Sending Discord alertparse error: Invalid escape at line 11, column 40 [ FAIL ] Sending Alert mcserver: Sending Discord alert: {"code": 50109, "message": "The request body contains invalid JSON."}

Expected behaviour

For the Discord alert to work without having to exchange a variable for a static servername.

Originally created by @Arthur-D on GitHub (Aug 30, 2022). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3973 ## User Story As a server administrator, I want Discord alerts to work without hassle for everyone so that they don't give up on getting alerts. ## Basic info * **Distro:** [Ubuntu 18.04.6] * **Game:** [Minecraft] * **Command:** [test-alert] * **LinuxGSM version:** [v22.1.0] ## Further Information Sending Discord alerts fails with a parse error, listed in the To Reproduce section of this bug report. I managed to work around it by changing line 21 in lgsm/functions/alert_discord.sh from ` "title": "${servername}",` to ` "title": "Minecraft",` and thus exchanging the variable for a static name. At first I thought the "invalid escape" bit in the error message meant I couldn't have a space in my Discord server name, so I changed its name from "Multiplayer Minecraft" to just "Minecraft" and made a new webhook, just in case. But it did not resolve the issue, so I had to go with the above workaround instead. ## To Reproduce Steps to reproduce the behaviour: 1. In my instance config lgsm/config-lgsm/mcserver/mcserver.cfg I added the Notification Alerts section from the template lgsm/config-lgsm/mcserver/_default.cfg 2. I followed https://docs.linuxgsm.com/alerts/discord but added the URL to my instance mcserver.cfg instead of common.cfg 3. I ran ./mcserver test-alert 4. See error: `[ .... ] Sending Alert mcserver: Sending Discord alertparse error: Invalid escape at line 11, column 40 [ FAIL ] Sending Alert mcserver: Sending Discord alert: {"code": 50109, "message": "The request body contains invalid JSON."}` ## Expected behaviour For the Discord alert to work without having to exchange a variable for a static servername.

kerem

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

closed this issue
added the
type: bug

distro: Ubuntu

info: docs

info: alerts

command: send
labels

kerem commented

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

Author

Owner

@malro57 commented on GitHub (Oct 7, 2022):

Have the same behavior here just after a fresh install of Memories Of Mars server. By the way my other server configured in the past still working as expected with test-alert.

@malro57 commented on GitHub (Oct 7, 2022): Have the same behavior here just after a fresh install of Memories Of Mars server. By the way my other server configured in the past still working as expected with test-alert.

kerem commented

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

Author

Owner

@Zxurian commented on GitHub (Nov 30, 2022):

This appears to still be happening, although I'm getting the error on a different line.

vaulthunters@minecraft-dedicated:/mnt/minecraft/vaulthunters$ ./mcserver test-alert
[ .... ] Sending Alert mcserver: UNAVAILABLEgrep: (standard input): binary file matches
[ WARN ] Sending Alert mcserver: More Info not enabled
[ .... ] Sending Alert mcserver: Sending Discord alertparse error: Invalid escape at line 11, column 120
[ FAIL ] Sending Alert mcserver: Sending Discord alert: {"code": 50109, "message": "The request body contains invalid JSON."}

I tried commenting out displayip value, however still got the same error with only discordwebhook defined within secrets-common.cfg

Edit:
Did some testing. I have 3 diffrent game servers with LGSM. Ark, Vlaheim, & Minecraft. The Ark & Valheim servers were both able to send discord alerts without issue. The Minecraft server will not and produces the Errors.

Of note - I am running two minecraft installations on the same server, and the Invalid escape is at different points in the code depending on the installation.
Installation 1 - user mcserver, installdir /mnt/minecraft/minecraftserver/, error is at line 11, column 44
Installation 2 - user vaulthunters, installdir /mnt/minecraft/vaulthunters/, error is at line 11, column 120

@Zxurian commented on GitHub (Nov 30, 2022): This appears to still be happening, although I'm getting the error on a different line. ``` vaulthunters@minecraft-dedicated:/mnt/minecraft/vaulthunters$ ./mcserver test-alert [ .... ] Sending Alert mcserver: UNAVAILABLEgrep: (standard input): binary file matches [ WARN ] Sending Alert mcserver: More Info not enabled [ .... ] Sending Alert mcserver: Sending Discord alertparse error: Invalid escape at line 11, column 120 [ FAIL ] Sending Alert mcserver: Sending Discord alert: {"code": 50109, "message": "The request body contains invalid JSON."} ``` I tried commenting out `displayip` value, however still got the same error with only `discordwebhook` defined within `secrets-common.cfg` Edit: Did some testing. I have 3 diffrent game servers with LGSM. Ark, Vlaheim, & Minecraft. The Ark & Valheim servers were both able to send discord alerts without issue. The Minecraft server will not and produces the Errors. Of note - I am running two minecraft installations on the same server, and the Invalid escape is at different points in the code depending on the installation. Installation 1 - user `mcserver`, installdir `/mnt/minecraft/minecraftserver/`, error is at `line 11, column 44` Installation 2 - user `vaulthunters`, installdir `/mnt/minecraft/vaulthunters/`, error is at `line 11, column 120`

kerem commented

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

Author

Owner

@theroflcopterguy commented on GitHub (Jul 18, 2023):

You need to change the motd in the server properties, i had same issue and this fixed it!!

@theroflcopterguy commented on GitHub (Jul 18, 2023): You need to change the motd in the server properties, i had same issue and this fixed it!!

kerem commented

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

Author

Owner

@egeexyz commented on GitHub (Aug 5, 2023):

You need to change the motd in the server properties, i had same issue and this fixed it!!

Can confirm this! I had a \ in the server title. Saw this post, removed it, and poof ~ it worked!

@egeexyz commented on GitHub (Aug 5, 2023): > You need to change the motd in the server properties, i had same issue and this fixed it!! Can confirm this! I had a `\` in the server title. Saw this post, removed it, and poof ~ it worked!

kerem commented

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

Author

Owner

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

Game server admins sometimes like to use all sorts of unusual characters for server name that can sometimes cause issues with being parsed in bash. \ is an example of this as in bash \ is an escape character. There isn't much I can really do as far as I can tell to get around this issue

@dgibbs64 commented on GitHub (Oct 20, 2023): Game server admins sometimes like to use all sorts of unusual characters for server name that can sometimes cause issues with being parsed in bash. \ is an example of this as in bash \ is an escape character. There isn't much I can really do as far as I can tell to get around this issue

kerem commented

2026-02-27 03:03:49 +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.

kerem referenced this issue

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

[PR #2565] [MERGED] feat(ts3server): converted to use tmux #3705