Page reload on "Lost connection to the socket server. Reconnecting" on Android with Google Chrome

[Bruceforce]

📑 I have found these related issues/pull requests

Several related issues:

• Seemingly Random "Cannot connect to the socket server. [Error: websocket error] Reconnecting..." #3519
• WebSocket Error with Uptime-Kuma #3769
• page error message“Lost connection to the socket server. Reconnecting...” #4409
• Got "Lost connection to the socket server. Reconnecting..." everytime when I open kuma site, how can I check the log? #4422
• Error: Lost connection to the socket server. Reconnecting. #6535
• socket.io: login emitted from the connect callback is silently dropped (handlers registered after an await) #7710

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Description

When using Google Chrome (version 151.0.7922.137) on Android 16 I receive the message Lost connection to the socket server. Reconnecting... every time I only shortly switch to another app.

I want to emphasize that I can see similar behavior on some other web apps using sockets (such as Komodo), but they are re-establishing the connection somehow without triggering a full page reload. The annoying part in uptime-kuma ist that this error triggers a whole reload of the page instead of trying to re-establish the socket connection in the background somehow. For example if I want to edit a config on my phone and need to look up something in another app (password, ports, protocol, whatever) and come back to Chrome the page gets auto reloaded and all my inputs are gone and I need to start over again.

Since this was requested on other issues I linked above, I also wanted to mention that this is fully reproducible on the demo page also. Therefore, I doubt this is an issue with my reverse proxy config.

👟 Reproduction steps

1. Open uptime-kuma in Chrome for Android
2. Switch to another app for about 5 to 10 seconds
3. Switch back to Chrome

👀 Expected behavior

uptime-kuma should try to re-establish the connection without forcing a full page reload losing all inputs.

😓 Actual Behavior

uptime-kuma forces a full page reload and all inputs are gone.

🐻 Uptime-Kuma Version

Version: 2.5.0 Frontend Version: 2.5.0

💻 Operating System and Arch

Linux 6.12.101+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.101-1 (2026-08-05)

🌐 Browser

Google Chrome on Android (version 151.0.7922.137)

🖥️ Deployment Environment

• Runtime Environment:
  • Docker: Docker version 29.7.2, build a7dcaa6
  • Docker Compose: Docker Compose version v5.4.0
• Database:
  • SQLite: Embedded
• Database Storage:
  • Filesystem:
    • Linux: ext4
  • Storage Medium: NVMe
• Uptime Kuma Setup:
  • Number of monitors: 6

I'm using traefik as reverse proxy and follow the setup guide in https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy so my config looks like this (tls settings and resolver are configured in traefik centrally, but that shouldn't matter):

    labels:
      - traefik.enable=true
      - traefik.http.routers.uptime-kuma.rule=Host(`...`)
      - traefik.http.routers.uptime-kuma.entryPoints=https
      - traefik.http.services.uptime-kuma.loadbalancer.server.port=3001

📝 Relevant log output

2026-08-16T10:39:19+02:00 [SOCKET] INFO: New polling connection, IP = 192.168.0.171