⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

I have recently upgraded from I believe 1.17.x to 1.18.5.

Now my previously set up Slack notification channel is no longer working. When I test the notification I get the following error popup: "Error: Error: queryAaaa ESERVFAIL hooks.slack.com"

If I'm interpreting my google search correctly there is some issue for Kuma resolving the IP-address for hooks.slack.com, tho I believe that issue does not lie with slack or the DNS because I was able to send a message to the slack channel through the URL in my terminal.

I am running Kuma behind a reverse proxy and inside the official docker container, although that has never been an issue so far, as the notifications had worked flawlessly before.

I also tested with a second slack app just to be on the safe side, but same result.

👟 Reproduction steps

1. Got to Settings->Notifications
2. Click on Setup Notification
3. Select Slack
4. Enter the Webhook URL provided by your existing or new Slack App
5. Click test

👀 Expected behavior

I would expect Kuma to successfully send a notification in to the channel configured in the Slack App

😓 Actual Behavior

A popup is displayed reading "Error: Error: queryAaaa ESERVFAIL hooks.slack.com" and no notification arrives in the channel

🐻 Uptime-Kuma Version

1.18.5

💻 Operating System and Arch

Ubuntu 22.04 LTS

🌐 Browser

Google Chrome Version 107.0.5304.87 (Official Build) (arm64)

🐋 Docker Version

Docker version 20.10.12, build 20.10.12-0ubuntu4; docker-compose version 1.29.2, build unknown

🟩 NodeJS Version

No response

📝 Relevant log output

No response