HTTP monitors all have a status of "canceled" after update to 1.23.4

[baubie]

⚠️ 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

HTTP monitors all showing "canceled" after update to 1.23.4 and it must be related to #3961 (comment)

When I checked, the timeout for these monitors were all set to 2880 seconds (I don't think I set this). I set them down to something more reasonable (a couple of seconds) and all monitors work again.

I didn't see any other posts about this and it may just affect me as I've been running Uptime Kuma for a long time now.

FIX: Update the timeout of your HTTP monitors to a new value.

👟 Reproduction steps

Have old monitors and upgrade to 1.23.4 (from 1.23.2 in my case).

👀 Expected behavior

Monitors will report being up.

😓 Actual Behavior

Monitors reported down with the status "canceled".

🐻 Uptime-Kuma Version

1.23.4

💻 Operating System and Arch

UBuntu 22.04

🌐 Browser

N/A

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[RoiArthurB]

Same here.

As a workaround, I noticed that enabling Ignore TLS/SSL error for HTTPS websites does fix this issue and makes the monitor works as before.

[louislam]

Ops, that is strange. I thought I handled it. Need to investigate.

I thought #4011 was fixed issue, but clearly not.

Do you guys know how to use SQLite Expert to view data? I want to see what is inside your timeout field.

[kWAYTV]

Ops, that is strange. I thought I handled it. Need to investigate.

I thought #4011 was fixed issue, but clearly not.

Do you guys know how to use SQLite Expert to view data? I want to see what is inside your timeout field.

Same issue here, clean first time install. Screenshot:

[chakflying]

I tried reproducing this by creating a new database in branch 1.21.X, adding HTTP monitors with intervals 60 and 360, then upgrading to 1.23.X, but it still works fine as expected.

Maybe you can post the config of the monitor here (masking out anything sensitive), and the node.js version used (or docker).

[megosugit]

Same here.

As a workaround, I noticed that enabling Ignore TLS/SSL error for HTTPS websites does fix this issue and makes the monitor works as before.

not for me :(

[CommanderStorm]

@chakflying noted in #4033 that

This may be a security fix in node.js v17+. Is the server running behind a corporate VPN/firewall?

(Related: nodejs/node#45378, blog post)

Could the people affected please report:

• if you are running behind a corporate firewall
• what version of node/docker you are running on

[chakflying]

I don't think #4033 is related to this since that has a specific error message.

[kokofixcomputers]

Ops, that is strange. I thought I handled it. Need to investigate.

I thought #4011 was fixed issue, but clearly not.

Do you guys know how to use SQLite Expert to view data? I want to see what is inside your timeout field.

Thats a weird issue! So this only happened after upgrading to 1.23.4? and should i upgrade to 1.23.4? or should i wait?

[JMyrng]

After downgrading to 1.23.3 the monitors are up and running again.

[megosugit]

After downgrading to 1.23.3 the monitors are up and running again.

is it safe to downgrade while keeping all data ? Is it just a matter of pulling 1.23.3 and recreating the container ?
@JMyrng :)

[JMyrng]

After downgrading to 1.23.3 the monitors are up and running again.

is it safe to downgrade while keeping all data ? Is it just a matter of pulling 1.23.3 and recreating the container ?
@JMyrng :)

Yes, I've done exactly that.

[megosugit]

After downgrading to 1.23.3 the monitors are up and running again.

is it safe to downgrade while keeping all data ? Is it just a matter of pulling 1.23.3 and recreating the container ?
@JMyrng :)

Yes, I've done exactly that.

thank you, I'm going to do the same as I keep receiving Cancelled notifications for no reason and my paused monitors get unpaused magically :/