Open krivahtoo opened 3 weeks ago
From the configuration and the log, i cannot see something obvious.
nginx
?
Could you send the SIGUSR1
signal
nginx -s reload
-e UPTIME_KUMA_WS_ORIGIN_CHECK=bypass
option (see https://github.com/louislam/uptime-kuma/releases/tag/1.23.9)?
- (getting the stupid stuff out off the way first) have you maybe not applied a change in
nginx
?
Yeah, I have
- are you using a custom filter set as the user in
/socket.io
isPOST
ed withcontent-type: text/plain
and tripsModSecurity OWASP
rulesΒ #4256, or are you running vanilla nginx?
I am running vanilla nginx.
- As a hunch: could you try launching the docker container with the
-e UPTIME_KUMA_WS_ORIGIN_CHECK=bypass
option (see https://github.com/louislam/uptime-kuma/releases/tag/1.23.9)?
I tried but still no change.
Should the ip on uptime-kuma
logs be my ip?
Are you running behind a firewall, vpn.. that might impede the websocket connection?
About the IP in the logs: https://github.com/louislam/uptime-kuma/blob/4794f9eb0bc47ebfe3eed3edaa7f880430052543/server/uptime-kuma-server.js#L138
=> we print the ip that we recive unless trustProxy
is set.
Are you running behind a firewall, vpn.. that might impede the websocket connection?
Not sure. I am using a gcp compute engine with the default allow-https/allow-http
firewall settings.
...
trustProxy
is set.
Do i need to set this? If so, where do i set it?
gcp compute engine with [...] firewall settings
Could you try disabling the fiewall and see if this fixes the problem? I don't know what that firewall filters as I don't use GCP.
Do i need to set this
You don't need to set this. (plus you can't if socketio is not working ^^)
Could you try disabling the fiewall and see if this fixes the problem?
I'm not sure if it is possible, I will check.
... I don't know what that firewall filters as ...
I think it basically block access to all ports on the server by default and you have to allow the ports you want accessible (allow-http
and allow-https
in this case allows traffic on ports 80
and 433
).
π I have found these related issues/pull requests
4797 The difference is I am using nginx config is from https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy#nginx
π‘οΈ Security Policy
Description
No response
π Reproduction steps
Start uptime-kuma docker image with the following:
Setup nginx reverse proxy with SSL (Certbot).
nginx config generated by Certbot:
uptime.example.com
on a browser.π Expected behavior
It should open the setup page and enable me to register and login to the dashboard.
π Actual Behavior
It just loads blank screen with error
Lost connection to the socket server. Reconnecting...
.Sometimes the error does not appear.
π» Uptime-Kuma Version
1.23.13
π» Operating System and Arch
Linux 6.1.0-18-cloud-amd64 Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
π Browser
Chromium 125.0.6422.141
π₯οΈ Deployment Environment
π Relevant log output