A fancy self-hosted monitoring tool
[!WARNING] The i18n detection mehanism which matches your languages and our languages introduced in #4244 was too basic (depending on your setup you might or might not be affected) See #4692 for further details.
[!WARNING] If you use proxys, please use
1.23.11
instead, as the more reliable events from #4630 don't take this part into consideration. If you want to prevent such breakages in the future, we would be very happy with increasing the test-coverage in general ^^
encodeBase64
for empty password or user in HTTP Basic Authentication (Thanks @Saibamen)navigator.languages
instead of navigator.language
for automatic language detection (Thanks @CommanderStorm)axios
, @actions/github
and dompurify
[1.23.X] (Thanks @Saibamen)UPTIME_KUMA_WS_ORIGIN_CHECK=bypass
in the previous version, you should remove it to enhance protection, unless you are using some 3rd-party plugins/apps.[!CAUTION] If you are using a reverse proxy, the security fix may cause connection issue to the WebSocket server. You should add
ProxyPreserveHost on
in your<VirtualHost>
for Apache, andproxy_set_header Host $host;
for Nginx. Read more: https://github.com/louislam/uptime-kuma/issues/4210#issuecomment-1849227424
[!WARNING] If you are using a 3rd-party frontend/tools this may be a breaking change, as the WebSocket Origin has to now match your server hostname. Set the environment variable
UPTIME_KUMA_WS_ORIGIN_CHECK=bypass
to skip this check. See GHSA-mj22-23ff-2hrr for further details.
aria-label
to the monitor search box (Thanks @CommanderStorm)ntfy
's priority
field (Thanks @CommanderStorm)ActionsSelect
and ActionsInput
having a default type="submit"
(Thanks @CommanderStorm)UPTIME_KUMA_WS_ORIGIN_CHECK
: cors-like
(default) and bypass
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
Retries
values from 1
to 0
getGameList
, testChrome
are no longer accessible without login[!WARNING] Update for Docker users: Since we updated the base image to Node.js 18 previously, the DNS resolver is a bit different for IPv6. Read more: https://github.com/louislam/uptime-kuma/issues/4027#issuecomment-1817783803
For testing timeout issue