Post actualizado el día October 24, 2026 by DeiviSanzPlay
XAMPP is the all-in-one package that installs Apache, MySQL, PHP, and Perl on your machine so you can set up a local server without hassle. When it works, it’s transparent. When it fails, the control panel stays red or the services shut down on their own a few seconds after you press Start. This guide walks through the most common causes and how to fix them without reinstalling everything from scratch.
Ports 80 and 443 are in use
This is the number one reason. Apache tries to listen on port 80 and another program is already using it: classic Skype, IIS, the World Wide Web Publishing service, or even a previous Apache instance that got stuck.
- Open a command prompt as administrator and run netstat -ano | findstr :80 to see the PID occupying the port.
- Locate the process with Task Manager and close it, or change Apache’s listening port.
- For the latter, edit httpd.conf (inside xamppapacheconf), find Listen 80 and change it to Listen 8080. Repeat in httpd-ssl.conf with 443.
After the change, your localhost will be http://localhost:8080. Remember to also update your projects’ configuration if they depend on the base URL.
MySQL stops immediately (port 3306)
MariaDB/MySQL uses 3306 by default. If you have another MySQL installation, Workbench with an embedded server, or an active Docker container, the port is taken. You can change the port in my.ini (port = 3306) or stop the conflicting service.
Another frequent cause is a corrupted ibdata1 after a sudden shutdown. The symptoms appear in mysql_error.log with messages about InnoDB. Before touching anything, copy the entire data folder. Then you can try starting with innodb_force_recovery = 1 and export the databases with mysqldump.
The control panel won’t open or shows “XAMPP is not running”
On Windows, this is usually due to permissions. Install XAMPP in C:xampp and run the panel as administrator. If the error mentions Access is denied, check that your antivirus isn’t blocking xampp-control.exe. Windows Defender sometimes quarantines the httpd.exe or mysqld.exe binaries after a signature update; add the XAMPP folder to the exclusions.
“Object not found” error or blank page
The server starts but can’t find your files. Check that the project is inside htdocs and that the URL matches the folder structure. A completely blank page almost always indicates a PHP error that isn’t being displayed: enable display_errors = On in php.ini and restart Apache.
Quick status check
Before touching any configuration, open http://localhost/dashboard/. If it loads, Apache is working and the problem is with your application. If it doesn’t load, check the logs: apachelogserror.log and mysqldatamysql_error.log contain the exact clue. Copying the last error line into a search engine usually saves half an hour of trial and error.
Prevention
Close XAMPP with the Stop button before shutting down your computer; this way you avoid InnoDB corruption. Keep a backup of htdocs and exported databases. And if you’re going to use multiple environments, consider Docker: it isolates ports and versions without fighting with the panel.
