Maintenance mode and time zones problem

[AndrewSpec]

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

There's a problem with maintanance mode and time zones (I think). After a fresh startup it's working fine. Next day it's ignoring the maintanance window.

When I'm posting this issue it should be in maintanance mode but it's not.

👟 Reproduction steps

Add a new maintanance task with UTC+2
Wait for that time.

👀 Expected behavior

In maintanance mode it should stop sending me notifications. But it's not entering maintanance mode.

😓 Actual Behavior

While it's time to fire the maintanance mode it's not doing it.

🐻 Uptime-Kuma Version

1.23.0

💻 Operating System and Arch

Debian 10

🌐 Browser

Brave

🐋 Docker Version

Docker 24.0.2

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[CommanderStorm]

• What is the maintenance window set to exactly? (what options are you using?)
• What exactly do you mean by Add a new maintanance task with UTC+2 (How did you add a maintanance period with a timezone? what is the timezone of the server, uptime-kuma and the maintanance period)
• why do you think this is a timezone issue? (what timezone are you running in?)

[AndrewSpec]

• What is the maintenance window set to exactly? (what options are you using?)

• What exactly do you mean by Add a new maintanance task with UTC+2 (How did you add a maintanance period with a timezone? what is the timezone of the server, uptime-kuma and the maintanance period)
• why do you think this is a timezone issue? (what timezone are you running in?)

It was working fine from the beginning but after some time I changed the time zone to my real time zone and then it stopped working. In the changelog I noticed that there was some fixes for the time zone so I thought that this could solve my problem but not.

[Besstheone]

Hello @AndrewSpec ,
Same Issue the workaround is to unset "Start Sate/Time" and "End Date/Time"

In fact without this workaround the maintenance mode is started and disabled instantly.

[AndrewSpec]

This workaround did the trick.

[louislam]

Cannot reproduce with 16:00 to 18:00.

[Besstheone]

Hello @louislam ,
I tested it with :

and it started /stopped in less than 1 sec

server time is the same as the last screenshot

[CommanderStorm]

#4634 does cover the same issue and has a deeper reproduction why this issue happens => closing as a "duplicate" (despite this beig first)