Skip to content

[Bug]: Termbin Details Link won't get posted on Discord Notification #4770

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Hornochs opened this issue Mar 26, 2025 · 2 comments · May be fixed by #4771
Open

[Bug]: Termbin Details Link won't get posted on Discord Notification #4770

Hornochs opened this issue Mar 26, 2025 · 2 comments · May be fixed by #4771

Comments

@Hornochs
Copy link
Contributor

User story

When a Discord notification is sent, the link to the termin.com Details won't get posted

Game

CS 1.6, CS:Source etc.

Linux distro

Debian 12

Command

command: start

Further information

On the Discord Notification Update the Payload doesn't post the Link to termin.com anymore.

Currently looks like:

Image

Previously it was:

Image

with settings

# More info | https://docs.linuxgsm.com/alerts#more-info
postalert="on"

Relevant log output

% ./cssserver stop                                                25-03-26 - 10:51:44
[  OK  ] Stopping cssserver: Graceful: sending "quit": 2 ... OK
[  OK  ] Post Details cssserver: termbin.com for 30D
[  OK  ] Stopping cssserver: Sending Discord alert

Steps to reproduce

  1. Setup Any Gameserver
  2. Setup Discord Webhook
  3. Enable postalert
  4. Start / Stop Server
@dgibbs64
Copy link
Member

Odd as I thought I had resolved that bug. I will have to take another look.

@dgibbs64 dgibbs64 moved this from 🆕 New Issues to 🏗 In Progress in LinuxGSM Backlog Mar 26, 2025
@Hornochs Hornochs linked a pull request Mar 28, 2025 that will close this issue
13 tasks
@Hornochs
Copy link
Contributor Author

@dgibbs64 My PR #4771 Fixes this Issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗 In Progress
Development

Successfully merging a pull request may close this issue.

2 participants