You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
... I have understood that answers are voluntary and community-driven, and not commercial support.
... I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description
It seems like the watchdog webhook doesn't include information about the issue but only the path to a temporary file in the body.
Logs:
Can't produce them currently, but I will submit them later
Steps to reproduce:
1. Configure a webhook for the watchdog (in my case discord)
my config:
WATCHDOG_NOTIFY_WEBHOOK=https://discord.com/api/webhooks/redacted
WATCHDOG_NOTIFY_WEBHOOK_BODY='{"content":null,"embeds":[{"title":"${SUBJECT}","description":"${BODY}","color":5814783}],"username":"mailcow Watchdog","avatar_url":"https://docs.mailcow.email/assets/images/favicon.png","attachments":[]}'
2. trigger any kind of notifications (for example a ip ban), except the monitoring started message
3. See the message from the bot
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12
Server/VM specifications:
ETH-Services GIANFAR: 4 vCores, 8GB RAM, 80GB SSD
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
kvm
Docker version:
27.3.1
docker-compose version or docker compose version:
v2.29.7
mailcow version:
2024-11
Reverse proxy:
No
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: