Active monitor does not record heartbeats

[Roiskia]

📑 I have found these related issues/pull requests

I have not found any simliar issues.

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

I have setup a new uptime kuma instance with one monitor as a bare metal service running on a windows machine but it does not produce any heartbeats with a the correct configuration (afaik).

The soap service i want to monitor is setup with ssl and is reachable through the browser. It is also in use, so i know this side is fine.
I have setup a http monitor for that service with an heartbeat interval of 20 seconds with a known, working request (tested in soapui). Uptime kuma and the soap service are both running on the same machine.

If i use the fqdn in the url, i wont get any heartbeats from this monitor. If i change the url to use localhost instead of the fqdn in the ssl cert, i get the expected errors Failing; Hostname/IP does not match certificate's altnames (...) at the expected heartbeat interval.

I have an identical setup on another machine in another, separate network that works fine, so im not sure whats happening here.

Is there a way to log what request are send by uptime kuma and what is happening with them?

👟 Reproduction steps

Install runtime and clone repo:

winget install OpenJS.NodeJS
winget install Git.Git
winget install CoreyButler.NVMforWindows
git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
$env:NODE_EXTRA_CA_CERTS='C:\path\to\ca\cert.pem'
node server/server.js

Configure monitor:

monitor type = http(s)
heartbeat interval = 20
retries = 0
heartbeat retry intervall = 20
request timeout = 4
resend notification if down x times = 0
max. redirects = 10
accepted status codes = 200-299
method = post
body encoding = xml
body = <request>
auth method = ntlm
user = user
password = ********
domain = domain

👀 Expected behavior

Regular heartbeats at the configured interval.

😓 Actual Behavior

No heartbeats.

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Windows Server 2022 x64

🌐 Browser

Edge

🖥️ Deployment Environment

• Runtime: nodejs 18.20.4 / npm 10.7.0
• Database: sqlite
• Filesystem used to store the database on: Windows
• number of monitors: 1

📝 Relevant log output

No response

[Roiskia]

Through the logs in the soap service, i found out that it is recieving requests. Somehow uptime kuma isnt showing me these heartbeats though.

I managed to let the kuma instance freez up as the web client lost the connection. After sending the process a ctrl+c in the terminal it resumed to working again. I also got a message about running into the request timeout and the web client updated accordingly this one time. Though i didnt get any further heatbeats until i could reproduce this freez.

[Roiskia]

After a few days of observing these systems, i got a few failed heartbeats, as they got restarted. So for some reason it seems like the successfull heartbeats are just ignored. Though i have no idea why this might be the case.