Database Offline

The database server at 127.0.0.1 appears to be offline.

Click here to attempt to setup the database. Sometimes this works.
Be sure the username and password to MySQL is the same as configured in includes/database-config.inc
Be aware that MySQL disables password authentication for root user upon installation or update in some systems. This may happen even for a minor update. Please check the username and password to MySQL is the same as configured in includes/database-config.inc
A video is available to help reset MySQL root password
Check the error message below for more hints
If you think this message is a false-positive, you can opt-out of these warnings below

Database Diagnostics Information

Database Error message:

Database host: 127.0.0.1

Database post: 3306

Database username: root

Database password: Ptbi2020!

Database name: mutillidae

IP resolved from database hostname: 127.0.0.1

Ping database results:

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.077 ms

--- 127.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.077/0.077/0.077/0.000 ms

Traceroute database results:

sh: traceroute: command not found

Port scan database results: The database is reachable. Connected to database host 127.0.0.1 on port 3306

LDAP Diagnostics Information

LDAP host: 127.0.0.1

LDAP post: 389

LDAP username: cn=admin,dc=mutillidae,dc=localhost

LDAP password: mutillidae

LDAP base DN: dc=mutillidae,dc=localhost

IP resolved from LDAP service hostname: 127.0.0.1

Ping LDAP service results:

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.062 ms

--- 127.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.062/0.062/0.062/0.000 ms

Traceroute LDAP service results:

sh: traceroute: command not found

Port scan LDAP service results: Cound not connect to LDAP service host 127.0.0.1 on port 389. The hostname or port may be incorrect, the server offline, the service is down, or a firewall is blocking the connection. 111 - Connection refused


Opt out of database warnings

You can opt out of database connection warnings for the remainder of this session