DBeaver cannot download the PostgreSQL driver from Maven
Maven artifact:org.postgresql:postgresql:RELEASE' can't be resolved in External RepositoriesShort answer
DBeaver downloads the PostgreSQL JDBC driver from a Maven repository the first time you connect. If it cannot reach the repository, or the driver entry uses a version it cannot resolve, you see this error. Fix the proxy or network, set a concrete driver version, or add the JAR by hand.
Fix it fast
1Find out which cause you have
Open the driver's library list and press Download/Update on the failing entry. The result tells you whether the network is the problem or the entry itself.
Database > Driver Manager > PostgreSQL > Edit > Libraries tab > Download/Update2Match what you see, then jump to its fix
- 1
Download/Update fails for every driver, not only PostgreSQL, on a company or restricted network.The download needs a proxy or repository settingFix - 2
Only the PostgreSQL entry fails, and its artifact version reads RELEASE.The driver entry points at a version that cannot be resolvedFix - 3
Download/Update still fails after the network settings are correct.The repository stays unreachable, so the JAR must be added by handFix
- 1
What does the error look like?
Maven artifact:org.postgresql:postgresql:RELEASE' can't be resolved in External RepositoriesThe PostgreSQL driver files are missing and the download does not complete
Cause 1 of 3
The download needs a proxy or repository setting
1Check
DBeaver says network configuration for driver downloads lives in the Drivers page of its preferences, where proxy host, port, credentials and file repositories are set.
Window > Preferences > Connections > Drivers2Fix
Enter the proxy details or repository your network requires, then retry Download/Update.
Window > Preferences > Connections > Drivers: set proxy host, port and credentials; then Download/Update3Verify
The library entry downloads and Test Connection passes.
Press Test Connection in the connection settingsConfirmed by dbeaver.com
Cause 2 of 3
The driver entry points at a version that cannot be resolved
1Check
The Libraries tab lists Maven artifacts that you can open by double-clicking. A Maven artifact is written as group:artifact_name:version.
Driver Manager > PostgreSQL > Edit > Libraries > double-click the postgresql artifact2Fix
Set the artifact to a concrete released version, for example the current stable PostgreSQL JDBC release listed on the project's download page, then press Download/Update.
org.postgresql:postgresql:42.7.143Verify
The library list shows a downloaded file for that version.
Press Test ConnectionConfirmed by dbeaver.com
Cause 3 of 3
The repository stays unreachable, so the JAR must be added by hand
1Check
DBeaver's own troubleshooting steps say to add a local JAR with Add File when the download keeps failing. The PostgreSQL project publishes the driver JAR (for example postgresql-42.7.14.jar, Java 8 or newer) on its download page.
java -version2Fix
Download the JAR from jdbc.postgresql.org on a machine that can reach it, remove the unresolved artifact, and press Add File to select the JAR.
Driver Manager > PostgreSQL > Edit > Libraries > Add File > select postgresql-42.7.14.jar3Verify
Use Find Class in the driver editor, then Test Connection.
Libraries > Find Class, then Test ConnectionConfirmed by dbeaver.com
How do I stop it coming back?
- Set the proxy in the preferences before the first connection on a restricted network.
- Keep a copy of the driver JAR on a shared drive for machines that cannot reach Maven.
- Pin an explicit driver version rather than a floating one.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Databases
DBeaver cannot run pg_restore: the utility is not found in the client home
Utility 'pg_restore' not found in client home '/usr/lib' (/usr/lib)
DBeaver runs pg_restore from a local PostgreSQL client folder; it does not bundle one.
3 causes, each with a fixDatabases
python manage.py migrate finishes but the tables for my app are missing
relation "myapp_book" does not exist
migrate only applies migration files that exist.
3 causes, each with a fixDatabases
Django save fails on PostgreSQL: null value in a column violates a not-null constraint
django.db.utils.IntegrityError: null value in column "price" of relation "shop_product" violates not-null constraint
A model field is NOT NULL in the database unless it has null=True.
3 causes, each with a fixDatabases
Django migration on PostgreSQL stops with 'pending trigger events'
django.db.utils.OperationalError: cannot ALTER TABLE "mytable" because it has pending trigger events
PostgreSQL runs a Django migration in one transaction.
2 causes, each with a fixDatabases
Django cannot connect to PostgreSQL: connection refused on port 5432, locally or in Docker
Is the server running on that host and accepting TCP/IP connections?
Connection refused means nothing accepted the connection at the host and port Django used.
4 causes, each with a fixDatabases
Django cannot connect to PostgreSQL through a pg_service.conf service
service file "C:\Users\you\AppData\Roaming\postgresql\.pg_service.conf" not found
Django passes a service name to PostgreSQL only through the OPTIONS dictionary, and libpq must find the file.
4 causes, each with a fix