This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Table of contents
- How to check driver version
- How to update driver version
- How to get logs
- UI freeze or SSO stuck
- UI doesn’t load or render correctly
How to check driver version
The easiest way to check your driver version:
- In Database Navigator, right-click your connection
- Click Edit Connection
- In the window that opens, click Test
- In the summary pop-up, check the Client version-that’s your driver
How to update driver version
To update a driver version:
-
As an administrator, go to Administration -> Driver Management
-
Open the driver
-
Go to the Libraries tab
-
Click Add file and upload the new version. You need to download the JAR file manually. Sources vary depending on the driver:
- Official vendor site-some drivers are only available on the database vendor’s site
- GitHub releases-many open-source drivers publish binaries in the Releases section
- Maven Central-some drivers are available at search.maven.org
- Other public repositories-some projects host drivers on project-specific sites or custom registries
-
Delete the old file, then click Save
Note
: In the Community edition, you can update drivers only on the server.
For details, see Driver Management.
How to get logs
To check logs for errors or connection issues, use one of the methods below.
In the UI
Go to Tools -> Log Viewer
In Docker
docker compose ps # find service name
docker logs <container_name> > container.log 2>&1
Tip: If the server won’t start after an update, run
docker compose ps -ato list all containers, including stopped ones.
In Kubernetes
kubectl get pods # list all pods
kubectl logs <pod_name> > pod.log 2>&1
Tip:
- add
-n <namespace>if your pods run in a custom namespace- use
kubectl logs <pod_name> -c <container_name>if the pod has multiple containers
In CloudBeaver AWS
If you deployed CloudBeaver on AWS, you can access logs through the AWS Console:
-
In the EC2 Console, find your instance
-
Click Connect
-
Use Session Manager or SSH
-
Run:
docker compose ps # find service name docker logs <container_name> > container.log 2>&1Tip: When you run
docker logs >> logs.txt, the file is saved inside the instance, in the directory where the command was run.
UI freeze or SSO stuck
If the UI looks normal but never updates, or SSO/login hangs, check if WebSockets are working:
-
In your browser, open DevTools -> Network
-
Filter by ws. You should see a
ws://<your-domain>/api/wsorwss://<your-domain>/api/wsrequest with status 101 Switching Protocols- if you see 101 and the connection stays open -> WebSockets are working
- if it’s missing, shows errors like 404/502/503, or closes quickly -> the proxy or firewall may be blocking WebSockets
-
If the connection closes quickly, increase proxy or load balancer timeouts
For details, see WebSockets.
Note
loads and works, but updates, task progress, and metadata changes may be delivered with a short delay compared to WebSockets.
UI doesn’t load or render correctly
This usually happens when you’re using an unsupported or outdated browser.
If the page doesn’t load, freezes, or parts of the UI are missing, try updating your browser or opening CloudBeaver in another supported one.
For more information, see Supported browsers.
CloudBeaver Documentation
- Getting started
- Create connection
- Connection network options
- Supported databases
- Drivers management

- Database authentication methods
- Database navigator
- Properties editor
- Data editor
- SQL editor
- Entity relation diagrams

- Cloud services
- AI Smart assistance
- Data transfer
- General user guide
- Administration
- Server configuration
- Server security and access configuration
- Authentication methods
- Access management
- Proxy configuration
- Secret management

- Logs
- Query manager
- Workspace location
- Command line parameters
- Session manager

- Deployment options
- CloudBeaver Editions
- FAQ
- Development