starred/cloudbeaver

Fork 0

mirror of https://github.com/dbeaver/cloudbeaver.git synced 2026-04-25 05:36:14 +03:00

[GH-ISSUE #3594] websocket connection error starting from 25.1.1 #1285

New issue

Closed

opened 2026-03-07 21:02:05 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 21:02:05 +03:00

Owner

Originally created by @roughnecks on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3594

Description

Hello.

Since docker version 25.1.1 I cannot login anymore to my cloudbeaver ce instance.
All i get are websocket errors in browser's console.
I'm running it on my LAN and access it via private-IP-address:port

https://sharer.woodpeckersnest.space/FuzE5/jogeBUYo61/raw.txt

Steps to reproduce

Upgrade from 24.3.5 to 25.1.1 and later versions
try to login
get websocket connection errors. login screen comes back at me and I am not logged in

Expected/Desired Behavior

I should be able to login as it was in the previous releases.

CloudBeaver Version

Cloudbeaver Community Ed 25.1.1

Additional context

Server OS: Debian Stable
Client Browser: latest Chrome/Firefox on Windows 10 up-to-date

Originally created by @roughnecks on GitHub (Jul 18, 2025). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3594 ### Description Hello. Since docker version 25.1.1 I cannot login anymore to my cloudbeaver ce instance. All i get are websocket errors in browser's console. I'm running it on my LAN and access it via `private-IP-address:port` https://sharer.woodpeckersnest.space/FuzE5/jogeBUYo61/raw.txt ### Steps to reproduce 1. Upgrade from 24.3.5 to 25.1.1 and later versions 2. try to login 3. get websocket connection errors. login screen comes back at me and I am not logged in ### Expected/Desired Behavior I should be able to login as it was in the previous releases. ### CloudBeaver Version Cloudbeaver Community Ed 25.1.1 ### Additional context <img width="632" height="714" alt="Image" src="https://github.com/user-attachments/assets/091a3a74-ea03-4529-ac49-5a3dc1c47ff2" /> Server OS: Debian Stable Client Browser: latest Chrome/Firefox on Windows 10 up-to-date

kerem

2026-03-07 21:02:05 +03:00

closed this issue
added the
deployment
label

kerem commented

2026-03-07 21:02:06 +03:00

Author

Owner

@dariamarutkina commented on GitHub (Jul 21, 2025):

Hello, @roughnecks !
Thanks for the ticket. Could you let us know precisely how you’re starting the application?

@dariamarutkina commented on GitHub (Jul 21, 2025): Hello, @roughnecks ! Thanks for the ticket. Could you let us know precisely how you’re starting the application?

kerem commented

2026-03-07 21:02:06 +03:00

Author

Owner

@roughnecks commented on GitHub (Jul 21, 2025):

Hi, I'm using docker compose

services:
    cloudbeaver:
        container_name: cloudbeaver
        tty: true
        stdin_open: true
        restart: unless-stopped
        ports:
            - 192.168.1.125:8978:8978
        volumes:
            - /opt/docker/cloudbeaver/workspace:/opt/cloudbeaver/workspace
        image: dbeaver/cloudbeaver:24.3.5

@roughnecks commented on GitHub (Jul 21, 2025): Hi, I'm using docker compose ``` services: cloudbeaver: container_name: cloudbeaver tty: true stdin_open: true restart: unless-stopped ports: - 192.168.1.125:8978:8978 volumes: - /opt/docker/cloudbeaver/workspace:/opt/cloudbeaver/workspace image: dbeaver/cloudbeaver:24.3.5 ```

kerem commented

2026-03-07 21:02:06 +03:00

Author

Owner

@dariamarutkina commented on GitHub (Jul 21, 2025):

Thanks!

Please add the following variables:

To your .env file:
CLOUDBEAVER_SECURE_COOKIES=false
To your .yml file (under environment):
- CLOUDBEAVER_SECURE_COOKIES=${CLOUDBEAVER_SECURE_COOKIES}

Please let us know whether this resolves the issue 🦫

@dariamarutkina commented on GitHub (Jul 21, 2025): Thanks! Please add the following variables: - To your .env file: `CLOUDBEAVER_SECURE_COOKIES=false` - To your .yml file (under environment): `- CLOUDBEAVER_SECURE_COOKIES=${CLOUDBEAVER_SECURE_COOKIES}` Please let us know whether this resolves the issue 🦫

kerem commented

2026-03-07 21:02:06 +03:00

Author

Owner

@roughnecks commented on GitHub (Jul 21, 2025):

It's fixed, yes.
Thanks

@roughnecks commented on GitHub (Jul 21, 2025): It's fixed, yes. Thanks