Uptime Kume dont detect 502 Bad Gateway as down
reddit / selfhosted

----------------------------------------------------------------------
fabio_teixei · 2023-12-29 20:44

Hello


I'm testing Uptime Kuma and it works fine when we have an 200 OK
status as UP or an 404 Not Found as DOWN, but if i have an 505 Bad
Gateway on the Uptime Kuma interface i still see as 200 OK but when i
try to access the site i can see the Bad Gateway on the screen.


The site is behind Traefik but on another host, is an external
service.

Do you know how to fix that?

----------------------------------------------------------------------
zoredache · 2023-12-29 21:11

If you use curl to retrieve the page in question with the `-D` option,
what is it showing as the result code?  The page displayed doesn't
really matter, at least for status checking.  The only thing that
matters is the code in the http headers. In some configurations you
might not get the backend http status code when the target is behind a
proxy.

    curl -D https://example.org/

    HTTP/2 200
    accept-ranges: bytes
    cache-control: public, max-age=0
    content-type: text/html; charset=UTF-8
    date: Fri, 29 Dec 2023 21:09:02 GMT
    etag: W/"529-18982b4cf78"
    last-modified: Sun, 23 Jul 2023 12:23:55 GMT
    x-powered-by: Express
    content-length: 1321

    ...

----------------------------------------------------------------------
fabio_teixei · 2023-12-29 21:26

the curl -D does not work, but here is the chrome developer tool
header:

----------------------------------------------------------------------
blind_guardian23 · 2023-12-30 12:22

Its not uptime kuma, his access works. do basic Debugging.