Does not work when using nginx reverse proxy about uptime-kuma HOT 6 OPEN

From the configuration and the log, i cannot see something obvious.

• (getting the stupid stuff out off the way first) have you maybe not applied a change in nginx?
  Could you send the SIGUSR1 signal

  nginx -s reload

• are you using a custom filter set as the user in #4256, or are you 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)?

from uptime-kuma.

• (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 is POSTed with content-type: text/plain and trips ModSecurity 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?

from uptime-kuma.

Are you running behind a firewall, vpn.. that might impede the websocket connection?

About the IP in the logs:

=> we print the ip that we recive unless trustProxy is set.

from uptime-kuma.

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?

from uptime-kuma.

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 ^^)

from uptime-kuma.

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).

from uptime-kuma.