How to Fix DVWA Database Connection Error: Causes, Checks, and Reliable Solutions

What the DVWA database connection error means

The DVWA database connection error usually appears when Damn Vulnerable Web Application cannot reach MySQL or MariaDB, cannot authenticate with the configured credentials, or cannot find the expected database.

This guide explains the most common causes and the exact fixes so you can get DVWA running again without guessing.

Because DVWA is often installed in Apache, XAMPP, WAMP, LAMP, Docker, or a virtual machine, the error can come from the web server, the database service, or a simple configuration mismatch.

Confirm that MySQL or MariaDB is running

The first thing to verify is that the database service is actually active.

If MySQL or MariaDB is stopped, DVWA cannot connect no matter how correct the username and password are.

• On Linux, check the service with systemctl status mysql or systemctl status mariadb.
• On XAMPP or WAMP, open the control panel and confirm the database module shows as running.
• In Docker, confirm the database container is healthy and listening on the expected port.

If the service is not running, start it and watch for startup errors.

Port conflicts, corrupted data directories, or missing dependencies can prevent MySQL from launching.

Check the DVWA configuration file

Most DVWA database issues come from incorrect settings in config/config.inc.php.

This file defines the database host, database name, username, and password that DVWA uses during connection.

Open the configuration file and verify these fields carefully:

• $_DVWA[ 'db_server' ] — usually 127.0.0.1, localhost, or a container hostname
• $_DVWA[ 'db_database' ] — commonly dvwa
• $_DVWA[ 'db_user' ] — commonly dvwa or root in a lab setup
• $_DVWA[ 'db_password' ] — must match the MySQL account password exactly

A very common mistake is using localhost when the environment expects 127.0.0.1, or vice versa.

In some PHP setups, localhost may try a socket connection while 127.0.0.1 uses TCP.

Make sure the DVWA database was created

DVWA needs its own database and schema.

If the database has not been created, the application may fail during login or setup.

Use MySQL or phpMyAdmin to confirm that the database exists.

If you are unsure, reinstall or initialize DVWA using its setup page after the database server is reachable.

• Open the DVWA setup page in your browser.
• Run the database initialization step if available.
• Refresh the page and confirm the setup completes successfully.

If the database exists but tables are missing, the initialization may have failed due to permissions or a SQL import error.

Verify database credentials and privileges

Even when the database and server are online, DVWA can still fail if the account lacks the proper privileges.

The MySQL user must be allowed to connect from the host where DVWA is running and must have permission to access the DVWA schema.

Check the following:

• The username in DVWA matches the MySQL account exactly.
• The password is correct and free of typo errors.
• The account has SELECT, INSERT, UPDATE, DELETE, and table creation permissions if needed for setup.
• The MySQL user is allowed to connect from the relevant host, such as localhost or a container network address.

For a local lab, many administrators create a dedicated DVWA MySQL user instead of using the root account.

That approach makes troubleshooting easier and reduces the risk of overprivileged access.

Check for host and port mismatches

Database connection errors also happen when DVWA points to the wrong host or port.

MySQL usually listens on port 3306, but some lab environments change this value.

Inspect the environment carefully:

• Confirm the database host is correct for your setup.
• Confirm the port in the database configuration matches the actual MySQL port.
• If using Docker, ensure both containers share the same network and the host name resolves correctly.

If MySQL is listening on a non-default port, update the DVWA configuration or use port forwarding so the application can reach the service.

Fix PHP MySQL extension problems

DVWA requires PHP to communicate with MySQL through extensions such as mysqli or pdo_mysql.

If those extensions are missing or disabled, DVWA may show a database connection failure even when MySQL is healthy.

Check your PHP installation and confirm the needed modules are enabled.

On Linux distributions, this may require installing an additional PHP package.

In XAMPP, WAMP, or similar stacks, it may require enabling the module in the control panel or configuration file.

Useful checks include:

• Run php -m and look for mysqli or pdo_mysql.
• Review the Apache or PHP error log for missing extension messages.
• Restart Apache or PHP-FPM after making changes.

Review file permissions and ownership

If Apache or PHP cannot read the DVWA configuration file, the application may fail before it can even reach MySQL.

Incorrect file permissions are especially common on Linux-based installations.

Confirm that the web server user can read the DVWA files and the configuration directory.

Also ensure the DVWA installation directory is owned by the correct user or group for your stack.

If you recently extracted the project from a ZIP file, permissions may have been inherited incorrectly.

Fix ownership, set readable permissions, and then reload the web server.

Inspect the error logs for the real cause

When DVWA does not connect to the database, the browser page often hides the detailed reason.

The server logs usually contain the real answer.

• Check Apache or Nginx error logs for PHP warnings and fatal errors.
• Check MySQL or MariaDB logs for authentication failures, socket errors, or startup issues.
• Review PHP logs if your stack separates application and web server logging.

Common log messages include access denied errors, unknown database errors, connection timeout messages, and socket path problems.

These messages usually point directly to the misconfiguration.

Handle common local and lab-specific scenarios

Different installation environments create different failure patterns.

Matching the fix to the setup saves time.

XAMPP or WAMP

• Make sure Apache and MySQL are both started from the control panel.
• Check whether another application is using port 3306.
• Confirm the PHP MySQL extension is enabled.

Linux LAMP stack

• Verify service status with system commands.
• Check /etc/php for the correct MySQL extension.
• Inspect file permissions under the web root.

Docker or virtual machines

• Use the correct database container name or internal hostname.
• Expose or map the MySQL port if DVWA connects from the host machine.
• Confirm container startup order if DVWA launches before the database is ready.

Use a quick troubleshooting checklist

If you want a fast way to isolate the problem, work through this checklist in order:

1. Confirm MySQL or MariaDB is running.
2. Verify the DVWA database name exists.
3. Check config/config.inc.php for correct host, user, password, and database values.
4. Confirm the MySQL user has the right privileges.
5. Make sure PHP has mysqli or pdo_mysql enabled.
6. Review Apache, PHP, and MySQL logs for exact error details.
7. Restart the web server and database after making changes.

Once these items are verified, most DVWA database connection errors can be resolved quickly and consistently.