BUNKERWEB - Lost connection to the socket server. Reconnecting...

[titi69lpb]

📑 I have found these related issues/pull requests

Hi don't fine any issue regarding BunkerWeb

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

error with configuration with bunkerweb : Lost connection to the socket server. Reconnecting...

👟 Reproduction steps

just setup with bunkerweb default parameter

👀 Expected behavior

IDK

😓 Actual Behavior

broken acces Lost connection to the socket server. Reconnecting...

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Docker

🌐 Browser

Chrome latest

🖥️ Deployment Environment

• Runtime: docker latest
• Database: by default
• Filesystem used to store the database on: docker internal
• number of monitors: 2

📝 Relevant log output

No response

[CommanderStorm]

Not a lot of information in your issue..

• How did you deploy precicely?
• What filters are set by BUNKERWEB?
• What are the server logs (both BUNKERWEB and uptime kuma), browser console and network tab?
• what is your network infrastructure? are you using a reverse proxy?
• 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 a unmodified reverse proxy?

[titi69lpb]

Hi @CommanderStorm thanks for the reply,k i'm not sure i'm able to answer all your questions.
Filters are by default in bunker excet i have disabled bad behavior

For the log of bunker it freeze when accesing it :/

For kuma i don't see anything revelant

==> Performing startup jobs and maintenance tasks
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Your Node.js version: 18.20.2
2024-08-13T16:31:26Z [SERVER] INFO: Welcome to Uptime Kuma
2024-08-13T16:31:26Z [SERVER] INFO: Node Env: production
2024-08-13T16:31:26Z [SERVER] INFO: Inside Container: true
2024-08-13T16:31:26Z [SERVER] INFO: Importing Node libraries
2024-08-13T16:31:26Z [SERVER] INFO: Importing 3rd-party libraries
2024-08-13T16:31:28Z [SERVER] INFO: Creating express and socket.io instance
2024-08-13T16:31:28Z [SERVER] INFO: Server Type: HTTP
2024-08-13T16:31:28Z [SERVER] INFO: Importing this project modules
2024-08-13T16:31:28Z [NOTIFICATION] INFO: Prepare Notification Providers
2024-08-13T16:31:28Z [SERVER] INFO: Version: 1.23.13
2024-08-13T16:31:28Z [DB] INFO: Data Dir: ./data/
2024-08-13T16:31:28Z [SERVER] INFO: Connecting to the Database
2024-08-13T16:31:28Z [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2024-08-13T16:31:28Z [DB] INFO: SQLite Version: 3.41.1
2024-08-13T16:31:28Z [SERVER] INFO: Connected
2024-08-13T16:31:28Z [DB] INFO: Your database version: 10
2024-08-13T16:31:28Z [DB] INFO: Latest database version: 10
2024-08-13T16:31:28Z [DB] INFO: Database patch not needed
2024-08-13T16:31:28Z [DB] INFO: Database Patch 2.0 Process
2024-08-13T16:31:28Z [SERVER] INFO: Load JWT secret from database.
2024-08-13T18:31:28+02:00 [SERVER] INFO: Adding route
2024-08-13T18:31:28+02:00 [SERVER] INFO: Adding socket handler
2024-08-13T18:31:28+02:00 [SERVER] INFO: Init the server
2024-08-13T18:31:28+02:00 [SERVER] INFO: Listening on 3001
2024-08-13T18:31:28+02:00 [SERVICES] INFO: Starting nscd

Here the setting for kuma in docker compose

  uptime-kuma:
    container_name: KUMA
    restart: always
    ports:
      - 3001:3001
    volumes:
      - /home/media/kuma/data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock
    image: louislam/uptime-kuma:latest
    networks:
      bw-services:
          aliases:
            - kuma
    labels:
      - "bunkerweb.SERVER_NAME=kuma.dimain.com"
      - "bunkerweb.USE_REVERSE_PROXY=yes"
      - "bunkerweb.REVERSE_PROXY_URL=/"
      - "bunkerweb.REVERSE_PROXY_HOST=http://kuma:3001"

For the last question i don't know :/

i also get message : Cannot connect to the socket server. [Error: xhr poll error] Reconnexion...

[CommanderStorm]

Please ask BUNKERWEB for support on how to access the log, how to add a rule to allow for the websocket traffic we need.
Without knowing why they blocked something, nothing can be done.
=> closing as not planned as I don't see how we can fix it on our side. If this changes and we were blocked for a good reason, we can reopen.

Tip

According to their docs, REVERSE_PROXY_WS defaults to no => you currently are blocking websocket connections

[titi69lpb]

Thanks for the help i'll check :)