FAQ

How to check driver version

The easiest way to check your driver version:

1. In Database Navigator, right-click your connection
2. Click Edit Connection
3. In the window that opens, click Test
4. In the summary pop-up, check the Client version-that’s your driver

How to update driver version

To update a driver version:

1. As an administrator, go to Administration -> Driver Management
2. Open the driver
3. Go to the Libraries tab

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

5. 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 -a to 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:

1. In the EC2 Console, find your instance
2. Click Connect
3. Use Session Manager or SSH

4. Run:

   docker compose ps  # find service name
   docker logs <container_name> > container.log 2>&1
   

   Tip

   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:

1. In your browser, open DevTools -> Network

2. Filter by ws. You should see a ws://<your-domain>/api/ws or wss://<your-domain>/api/ws request with status 101 Switching Protocols

   Info

   • 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

3. If the connection closes quickly, increase proxy or load balancer timeouts

For details, see WebSockets.