Mamp apache server won t start

New Page

  1. House
  2. Resource Center
  3. Database
  4. MAMP
  5. How To Fix Apache Server Not Starting In MAMP Error (In 4 Steps)

How to fix the Apache server that no se inicia en el error MAMP (in 4 steps)

Last update: September 16, 2022

After resolving the "El servidor Apache no se inicia" error in MAMP.Circle

The local installations of WordPress are an excellent way to test the cambios in su site antes de ponerlos en marche, y MAMP es una de las mjores de las configurar uno. Sin embargo, eso puede ser difícil cuando Apache, uno de los componentes clave de MAMP, se niega a iniciarse.

Hay varias razones por las que su servidor Apache podría fallar al ejecutarse. Algo podría estar blocando el puerto que usa; podría haber otra instantiation of Apache que ya se esté ejecutando; o may have an incompatibility with the version of PHP that is used in MAMP.

¿Apurado? Save this article as a PDF.

¿Cansado de desplazarse? Download a PDF version to learn more easily.

To download

Luckily, these issues are all fairly simple to troubleshoot and fix.

In this article, we will explain some of the possible causes for the Apache MAMP server not starting error and how to fix them. Let’s start!

Contents

  1. Causes of Apache server not starting in MAMP error
  2. Step 1: Make sure Skype is not running
  3. Step 2: Make sure no other Apache instance is running
  4. Step 3: Stop Apache from the command line
  5. Step 4: Change the PHP version in your MAMP preferences

Causes of Apache server not starting in MAMP error

Before we dive into the causes of this error, let’s cover some basics. A MAMP installation is actually a bundle of several software components that work together: the Apache web server, the MySQL database software, and the PHP programming language.

Each of these components is vital to the operation of your local installation. If one is missing or encounters an error, you won’t be able to access or work with your WordPress testing environment.

When you open the MAMPapp on your computer, the Apache server and MySQL should start up automatically, bringing your local site “online” and enabling you to access it. However, you may find that sometimes the Apache server fails to start, which is likely why you’re here.

You may sometimes see a pop-up with the error message “Apache could not be started. Please check your MAMP installation and configuration. However, you often won’t see any error message — instead, the dot next to Apache Server in the MAMP window will not turn green:

La luz del servidor Apache en la ventana MAMP no se volverá verde si no se inicia.The Apache server light in the MAMP window will not turn green if it is not starting.

There are several possible causes for the Apache MAMP server not starting:

  • Something is blocking the port used by the Apache server. Skype is a common culprit.
  • Another instance of Apache is already running on your computer.
  • There is an incompatibility between the versions of Apache and PHP used.

Heureusement, ces problèmes sont tous relativement faciles à dépanner et à résoudre. Dans la section suivante, nous verrons exactement comment procéder.

Now that you know what the problem is, you can start troubleshooting. There are four different fixes that may resolve the “Apache server not starting” error in MAMP. We recommend trying each in order, and only moving on to the next one if the issue persists.

Important

Looking for a free and powerful local WordPress development tool? DevKinsta features quick and easy site creation, email and database management tools, one-click PHP version switching, and full integration with MyKinsta. Get started with DevKinsta today, even if you’re not a Kinsta customer.

Step 1: Ensure That Skype Is Not Running

The Skype communications app has a tendency to occupy the port that Apache uses on the network, preventing it from starting.

Fixing this is incredibly simple – just close Skype and restart MAMP.

If conflicts persist and you need MAMP and Skype to run at the same time, you can change the port that Apache uses. To do this, navigate to MAMP > Preferences in the MAMP application menu:

You can use Apache to avoid conflicts with Skype and other applications.You can change the port used by Apache to avoid conflicts with Skype and other applications.

Cliquez sur Ports en haut de la fenêtre Préférences , entrez un nouveau port pour Apache et cliquez sur OK pour enregistrer la modification. Le port 8080 est une option couramment utilisée pour éviter les conflits, mais vous pouvez ajouter ici la valeur que vous souhaitez.

Enregistrez-vous pour recevoir le bulletin d’informations

S’inscrire maintenant

En soumettant ce formulaire, j’accepte les conditions générales et la politique de confidentialité, y compris le transfert de données aux États-Unis. En partageant votre e-mail, vous acceptez également de recevoir des informations occasionnelles liées aux services, événements et promotions de Kinsta. Vous êtes libre de vous désabonner à tout moment.

Want to know how we increased our traffic by over 1000%?

Join over 20,000 other people who receive our weekly newsletter with insider WordPress tips!

Subscribe Now Step 2: Make sure no other instances of Apache are running

If you don’t use Skype, or the above fix didn’t resolve the problem, the next thing to check is that no other instances of Apache are already running. This is a common reason why the MAMP Apache server won’t start. First, close MAMP on your computer. Next, you’ll need to pull up your computer’s Task Manager (Activity Monitor on Mac devices).

To open the Task Manager in Windows, you can either press Ctrl + Alt + Delete and select Task Manager from the menu, or open the Start menu and search for “Task Manager”. On a Mac, you can open the Activity Monitor from inside the Applications menu.

Once it’s opened, head to the Processes tab in the Task Manager in Windows, or the CPU tab on a Mac:

Busque instances of "httpd" or "Apache" in the Administrador de tareas para encontrar otros Apache servidores que puedan estar blocando MAMP.Look for instances of “httpd” or “Apache” in Task Manager to find other Apache servers that may be blocking MAMP.

Recherchez « httpd » ou « Apache » dans la liste des processus. Si vous êtes sur un Mac, vous pouvez utiliser le champ de recherche en haut à droite pour vous faciliter la tâche, mais sous Windows, vous devrez effectuer une recherche manuelle. Heureusement, les processus sont classés par ordre alphabétique.

Quittez chaque processus “httpd” ou “Apache” que vous trouvez en cliquant dessus avec le bouton droit de la souris et en sélectionnant Fin de tâche . Redémarrez ensuite MAMP pour voir si le problème est résolu.

Étape 3 : Arrêtez Apache à partir de la ligne de commande

If the previous step didn’t work, you can try to globally stop all instances of Apache on your computer using the command line. In Windows, open the PowerShell application by right-clicking on the Start menu and selecting it from the menu. On a Mac, open the Terminal app in ~/Utilities/Terminal.

Then enter the following command:

apache -k stop

Once you type it, press Enter or Return to run the command. Then try restarting the MAMP app to see if it works.

Step 4: Change the PHP version in your MAMP preferences

Finally, if none of the above solutions worked, the problem may be an incompatibility between the Apache and PHP versions used. To solve this problem, you can change the PHP version used by MAMP.

In the MAMP window, navigate to MAMP > Preferences , then click the PHP tab at the top of the screen:

Puede intendar to change the version of PHP used in MAMP to solve the problems with the Apache server that has not been launched.You can try changing the PHP version used in MAMP to fix issues with Apache server not starting.

Cliquez sur le menu déroulant à côté de “Version standard” et sélectionnez un numéro de version différent dans la liste. Il n’y a peut-être que deux choix, mais s’il y en a plus, vous pouvez les essayer individuellement jusqu’à ce que l’un fonctionne. Nous vous recommandons de commencer par la version la plus récente et de revenir en arrière.

Lorsque vous avez terminé, cliquez sur OK pour enregistrer vos modifications. Redémarrez ensuite MAMP pour vous assurer que le problème a été résolu.

Sommaire

Testing your site on a local MAMP installation is a smart idea, and it can help you iron out any problems before the content is pushed live. However, when something goes wrong with that local setup, it can be frustrating.

If you find that the MAMP Apache server won’t start, try these troubleshooting steps:

  1. Ensure that Skype isn’t running, as it can interfere with the Apache server.
  2. Verify that no other instances of Apache are running in the background.
  3. Stop all Apache instances using the command line.
  4. Change the PHP version used by MAMP.

To avoid the need for troubleshooting when your site goes live, consider hosting with Kinsta. Our managed WordPress hosting service is fast and reliable, and our 24/7 support is always available when you need it!

Save time, costs and maximize site performance with:

  • Instant help from WordPress hosting experts, 24/7.
  • Intégration Cloudflare Entreprise.
  • Audience mondiale avec 35 centres de données dans le monde.
  • Optimisation avec notre surveillance intégrée des performances des applications.

All this and more, in one plan with no long-term contracts, assisted migrations and a 30-day money-back guarantee. Check out our plans or talk to sales to find the plan that’s right for you.

  1. House
  2. Resource Center
  3. Database
  4. MAMP
  5. What to do if MAMP won’t start (5 best solutions)

What to do if MAMP won’t start (5 best solutions)

Last update: September 16, 2022

Qué hacer si MAMP no se iniciaclose

Having a local staging environment available is essential for WordPress developers. MAMP is a popular solution, but some common issues can prevent the platform from working properly.

Fortunately, MAMP users have found some fairly simple solutions to these issues, which you can use to get your local stack working again. Often, all it takes is a few clicks.

Press? Save this article in PDF format.

Tired of scrolling? Download a PDF version for easy offline reading and sharing with your colleagues.

To download

In this article, we’ll go over what MAMP is, why it’s useful, and how to find its error logs. Next, we’ll walk you through five common resolutions for MAMP not starting. Let’s get straight to the point!

Contents

  1. An introduction to MAMP
  2. How to Check Your MAMP Error Logs
  3. What to do if MAMP won’t start (5 best solutions)

An introduction to MAMP

MAMP is one of many popular local development platforms. It turns your computer into a server environment that can host websites while you work on it:

The MAMP homepage.The MAMP homepage.

MAMP uses Apache, MySQL, and PHP, making it highly compatible with WordPress. There is a free version available, or you can pay for a proprietary version that includes installers and other features to help you get your first site set up quickly and improve your workflow.

Like all sites hosted locally, your MAMP development or test website will not be publicly available. This enables you to build or test features freely, without worrying about it affecting your front-facing User Experience (UX). It also prevents visitors from stumbling upon your half-completed site.

See how Kinsta stacks up against the competition. Select your provider WP Engine SiteGround GoDaddy Bluehost Flywheel HostGator Cloudways AWS Digital Ocean DreamHost Other Compare

De plus, le développement local ne nécessite pas de connexion Internet, vous pouvez donc travailler de n’importe où. Les sites locaux ont également tendance à se charger plus rapidement, ce qui peut améliorer quelque peu votre productivité. Une fois que vous avez terminé de créer ou d’apporter des modifications à votre site, vous pouvez le migrer vers un serveur en direct.

Nous avons expliqué comment installer MAMP dans un article précédent. À ce stade, nous supposerons que vous l’avez déjà utilisé mais que vous avez rencontré un problème.

Comment vérifier vos journaux d’erreurs MAMP

Trouver vos journaux d’erreurs MAMP est assez simple. Accédez simplement au dossier dans lequel votre installation est enregistrée et ouvrez le dossier des journaux. Vous devriez voir des fichiers pour vos journaux d’erreurs Apache, MySQL et PHP :

MAMP error log files.MAMP error log files.

If you’re experiencing problems with MAMP not starting, this should be your first step. Check the logs to see if there are any messages related to the problem and whether they provide specific steps you can take to resolve it. This is much faster than trial and error troubleshooting.

What to Do If MAMP Is Not Starting (5 Top Solutions)

Some common issues MAMP users run into include Apache not starting and MySQL not starting. Either problem will keep the platform from running, making it impossible for you to access your local site. Here are some top solutions that should help you resolve both roadblocks, so you can get back to work.

1. Restore Your Document Root Folder

The document root of your MAMP installation is where your virtual host’s HTML, PHP, and image files are stored. Suppose you deliberately or accidentally changed or deleted your document root folder. In this case, you may see an error message stating “Apache could not be started. Please verify your MAMP installation and configuration” when you try to launch your server:

Apache could not start. Please check your MAMP installation and configuration.Apache could not start. Please check your MAMP installation and configuration.

Pour résoudre ce problème, il vous suffit de restaurer le dossier racine de votre document ou d’indiquer à MAMP où vous l’avez déplacé. Ce processus varie selon que vous utilisez un ordinateur Mac ou Windows, dans la mesure où les chemins d’accès aux fichiers peuvent être légèrement différents. Cependant, vous devriez pouvoir suivre les étapes ci-dessous sur l’un ou l’autre des systèmes d’exploitation (OS).

By default, the MAMP document root is located at Applications/MAMP/htdocs on macOS, or C:MAMPhtdocs on Windows. If you know where your new document root folder is, you can open your MAMP configuration file by navigating to Applications (or C:) > MAMP > conf > apache > httpd.conf, and then replacing the default path with the new one.

Info

Looking for a powerful tool for local WordPress development? DevKinsta features one-click site creation, built-in HTTPS, powerful email and database management tools, and more. Learn more about DevKinsta!

Once you open httpd.conf, search for mentions of “DocumentRoot” and replace the default path everywhere. Save the file, then stop and restart MAMP.

Alternatively, you can select your new document root via the MAMP control panel. Open the Preferences window and select the Web Server tab:

MAMP web server preferences.MAMP web server preferences.

Make sure Apache is selected. Next, click the Select button  next to Document Root. This will open a Finder window, where you can choose the folder you want to use as the document root.

Click Select once you’ve chosen the correct folder, then select OK in the MAMP Preferences window:

Confirming the MAMP document root in the Web Server Preferences window.Confirming the MAMP document root in the Web Server Preferences window.

This will reset your document root and automatically restart MAMP. Apache should then be able to start.

Register to receive the newsletter

Register now

By submitting this form, I agree to the Terms & Conditions and Privacy Policy, including data transfer to the United States. By sharing your email, you also agree to receive occasional information related to Kinsta services, events, and promotions. You are free to unsubscribe at any time.

Want to know how we increased our traffic by over 1000%?

Join over 20,000 other people who receive our weekly newsletter with insider WordPress tips!

Subscribe now

2. Change your listening port

By default, MAMP runs Apache on port 8888. If this port is in use by another application, Apache will fail to start.

To fix this, you can either quit the application preventing apache from connecting to port 8888 or change the listening port in your MAMP configuration file.

If you want to discover which app is blocking the port, you can use the command line to do so. The command you need to enter will vary depending on your OS:

  • macOS: sudo lsof -nP -iTCP:$PORT | grep LISTEN
  • Windows: netstat -ab | more

These should return a list of Process Identifiers (PIDs) and the ports they’re running on. You can terminate the process that is running on the port you need in order to start MAMP by using one of the following:

  • macOS: sudo kill -9 <PID>
  • Windows: taskkill /F /PID pid_number

When performing the above commands, make sure to substitute placeholders such as $PORT, <PID>, and pid_number with the appropriate values.

Si vous souhaitez modifier le port d’écoute dans votre fichier de configuration MAMP, vous pouvez le faire en ouvrant votre fichier httpd.conf et en remplaçant toutes les mentions de “port 8888” par “port 8000” (ou une autre alternative). Enregistrez le fichier, puis redémarrez Apache.

Additionally, you can change the Apache port in Preferences > Ports:

MAMP port preferences.MAMP port preferences.

Click OK  to save your changes.

Looking for a powerful tool for local WordPress development? DevKinsta offers one-click site creation, built-in HTTPS, powerful email and database management tools, and more. Learn more about DevKinsta!

3. Kill all MySQL processes and restart MAMP

If your MAMP issues are due to MySQL rather than Apache, there are a few fixes you can try. The problem is usually caused by another MySQL service running on the same port.

The easiest solution is to kill all MySQL processes and restart MAMP. On macOS, you can do this using Activity Monitor, which you’ll find in your computer’s Utilities folder.

Search for “mysqld”, select all running processes, then quit them by clicking the X button  in the upper left corner of the window:

Kill active MySQL processes via Activity Monitor.Kill active MySQL processes via Activity Monitor.

Windows users will need to open Resource Monitor from the Start menu:

The Windows Resource Monitor application.The Windows Resource Monitor application.

Locate the mysqld.exe file  , right-click it, and select End Process. Once you have exited all MySQL processes on your computer, stop and restart MAMP.

4. Clear your MySQL logs

If deleting all active MySQL processes on your computer does not allow MySQL to start, you can try deleting your MySQL log files. These are stored in your MAMP db/mysql57 directory:

MAMP MySQL log files.MAMP MySQL log files.

They should be named ib_logfile0, ib_logfile1, etc. Save the log files, then delete them and restart MAMP. Log files will automatically regenerate when needed again.

5. Delete the mysql.sock.lock file

MAMP doit écrire des identifiants de processus (PID) pour les processus actifs dans un fichier mysql.sock.lock. Si cette tâche échoue, le fichier est laissé au lieu d’être supprimé une fois le processus terminé.

Cela empêchera MySQL de démarrer, car il traite un fichier mysql.sock.lock vide de la même manière qu’un fichier contenant un PID en cours d’exécution. Pour résoudre ce problème, vous devrez supprimer le fichier manuellement.

Navigate to your MAMP files (Applications/MAMP on Mac or C:MAMP on Windows) and look for the tmp folder. Then select the mysql folder, search for the mysql.sock.lock file, and delete it. As with the log files, a new mysql.sock.lock file will automatically be created when it’s needed next.

Summary

MAMP is one of the local development solutions for many WordPress professionals and hobbyists (note: it’s not the only one). However, some issues may arise that will prevent your server from starting, and ultimately delay your workflow.

In this article, we walked you through five possible solutions if Apache or MySQL won’t start:

  1. Restore your document root folder.
  2. Change your listening port.
  3. Kill all MySQL processes and restart MAMP.
  4. Clear your MySQL logs.
  5. Delete the mysql.sock.lock file.

Économisez du temps, de l’argent et maximisez les performances du site avec :

  • Aide instantanée d’experts en hébergement WordPress, 24h/24 et 7j/7.
  • Intégration Cloudflare Entreprise.
  • Audience mondiale avec 35 centres de données dans le monde.
  • Optimisation avec notre surveillance intégrée des performances des applications.

All this and more, in one plan with no long-term contracts, assisted migrations and a 30-day money-back guarantee. Check out our plans or talk to sales to find the plan that’s right for you.

  1. House
  2. Resource Center
  3. Database
  4. MAMP
  5. How To Fix Apache Server Not Starting In MAMP Error (In 4 Steps)

How To Fix Apache Server Not Starting In MAMP Error (In 4 Steps)

Last update: September 16, 2022

Learn how to fix "Apache server not starting" error in MAMP.close

Local installations of WordPress are a great way to test changes to your site before going live, and MAMP is one of the best ways to set one up. However, this can be difficult when Apache, one of MAMP’s key components, refuses to start.

There are several reasons your Apache server might fail to run. Something could be blocking the port it uses; there could be another instance of Apache already running; or there might be an incompatibility with the version of PHP you’re using in MAMP.

In a hurry? Save this article as a PDF.

Tired of scrolling? Download a PDF version for easier offline reading and sharing with coworkers.

Download

Fortunately, these issues are all fairly simple to troubleshoot and fix.

In this article, we’ll explain some of the possible causes of the MAMP Apache server not starting error, and walk through how to fix each one. Let’s get started!

Table of Contents

  1. Causes of the Apache Server Not Starting in MAMP Error
  2. Step 1: Ensure That Skype Is Not Running
  3. Step 2: Make Sure No Other Instances of Apache Are Running
  4. Step 3: Stop Apache From the Command Line
  5. Step 4: Change the PHP Version in Your MAMP Preferences

Causes of the Apache Server Not Starting in MAMP Error

Before we dive into the causes of this error, let’s cover some basics. A MAMP installation is actually a bundle of several software components that work together: the Apache web server, the MySQL database software, and the PHP programming language.

Each of these components is vital to the operation of your local installation. If one is missing or encounters an error, you won’t be able to access or work with your WordPress testing environment.

When you open the MAMPapp on your computer, the Apache server and MySQL should start up automatically, bringing your local site “online” and enabling you to access it. However, you may find that sometimes the Apache server fails to start, which is likely why you’re here.

You may sometimes see a pop-up with the error message “Apache could not be started. Please check your MAMP installation and configuration. However, you often won’t see any error message — instead, the dot next to Apache Server in the MAMP window will not turn green:

The Apache server light in the MAMP window will not turn green if it is not starting.The Apache server light in the MAMP window will not turn green if it is not starting.

There are several possible causes for the Apache MAMP server not starting:

  • Something is blocking the port used by the Apache server. Skype is a common culprit.
  • Another instance of Apache is already running on your computer.
  • There is an incompatibility between the versions of Apache and PHP used.

Heureusement, ces problèmes sont tous relativement faciles à dépanner et à résoudre. Dans la section suivante, nous verrons exactement comment procéder.

Now that you know what the problem is, you can start troubleshooting. There are four different fixes that may resolve the “Apache server not starting” error in MAMP. We recommend trying each in order, and only moving on to the next one if the issue persists.

Important

Looking for a free and powerful local WordPress development tool? DevKinsta features quick and easy site creation, email and database management tools, one-click PHP version switching, and full integration with MyKinsta. Get started with DevKinsta today, even if you’re not a Kinsta customer.

Step 1: Ensure That Skype Is Not Running

The Skype communications app has a tendency to occupy the port that Apache uses on the network, preventing it from starting.

Fixing this is incredibly simple – just close Skype and restart MAMP.

If conflicts persist and you need MAMP and Skype to run at the same time, you can change the port that Apache uses. To do this, navigate to MAMP > Preferences in the MAMP application menu:

You can change the port used by Apache to avoid conflicts with Skype and other applications.You can change the port used by Apache to avoid conflicts with Skype and other applications.

Cliquez sur Ports en haut de la fenêtre Préférences , entrez un nouveau port pour Apache et cliquez sur OK pour enregistrer la modification. Le port 8080 est une option couramment utilisée pour éviter les conflits, mais vous pouvez ajouter ici la valeur que vous souhaitez.

Enregistrez-vous pour recevoir le bulletin d’informations

S’inscrire maintenant

En soumettant ce formulaire, j’accepte les conditions générales et la politique de confidentialité, y compris le transfert de données aux États-Unis. En partageant votre e-mail, vous acceptez également de recevoir des informations occasionnelles liées aux services, événements et promotions de Kinsta. Vous êtes libre de vous désabonner à tout moment.

Want to know how we increased our traffic by over 1000%?

Join over 20,000 other people who receive our weekly newsletter with insider WordPress tips!

Subscribe Now Step 2: Make sure no other instances of Apache are running

If you don’t use Skype, or the above fix didn’t resolve the problem, the next thing to check is that no other instances of Apache are already running. This is a common reason why the MAMP Apache server won’t start. First, close MAMP on your computer. Next, you’ll need to pull up your computer’s Task Manager (Activity Monitor on Mac devices).

To open the Task Manager in Windows, you can either press Ctrl + Alt + Delete and select Task Manager from the menu, or open the Start menu and search for “Task Manager”. On a Mac, you can open the Activity Monitor from inside the Applications menu.

Once it’s opened, head to the Processes tab in the Task Manager in Windows, or the CPU tab on a Mac:

Look for instances of "httpd" or "Apache" in Task Manager to find other Apache servers that may be blocking MAMP.Look for instances of “httpd” or “Apache” in Task Manager to find other Apache servers that may be blocking MAMP.

Recherchez « httpd » ou « Apache » dans la liste des processus. Si vous êtes sur un Mac, vous pouvez utiliser le champ de recherche en haut à droite pour vous faciliter la tâche, mais sous Windows, vous devrez effectuer une recherche manuelle. Heureusement, les processus sont classés par ordre alphabétique.

Quittez chaque processus “httpd” ou “Apache” que vous trouvez en cliquant dessus avec le bouton droit de la souris et en sélectionnant Fin de tâche . Redémarrez ensuite MAMP pour voir si le problème est résolu.

Étape 3 : Arrêtez Apache à partir de la ligne de commande

If the previous step didn’t work, you can try to globally stop all instances of Apache on your computer using the command line. In Windows, open the PowerShell application by right-clicking on the Start menu and selecting it from the menu. On a Mac, open the Terminal app in ~/Utilities/Terminal.

Then enter the following command:

apache -k stop

Once you type it, press Enter or Return to run the command. Then try restarting the MAMP app to see if it works.

Step 4: Change the PHP version in your MAMP preferences

Finally, if none of the above solutions worked, the problem may be an incompatibility between the Apache and PHP versions used. To solve this problem, you can change the PHP version used by MAMP.

In the MAMP window, navigate to MAMP > Preferences , then click the PHP tab at the top of the screen:

You can try changing the PHP version used in MAMP to fix issues with Apache server not starting.You can try changing the PHP version used in MAMP to fix issues with Apache server not starting.

Haga click on the drop-down menu together with “Standard version” and select a different version number from the list. Es possible que solo haya dos opciones, pero si hay más, puede probarlas individually hasta que una funcione. We recommend starting with the most recent version and working hacia atrás.

Cuando haya terminado, haga clic en Aceptar para guardar los cambios. Luego reinicie MAMP para asegurarse de que el problema se haya resuelto.

resume

Probar su sitio en una instalación MAMP local est une buena idea y puede ayudarlo a solucionar cualquier problema antes of que el contenido se public. Sin embargo, cuando dirty algo mal con esa local configuration, puede ser frustrating.

If you find that the MAMP Apache server does not start, you will not be able to solve problems:

  1. Asegúrese de Skype no se esté ejecutando, you may interfere with the Apache server.
  2. Verific que no se estén ejecutando otras instancias de Apache in segundo plano.
  3. Own all instances of Apache using the command line.
  4. Cambia the version of PHP used by MAMP.

To avoid the need to solve problems when your site is activated, consider alojarlo con Kinsta. ¡ Our WordPress hosting service is fast and reliable, and our new 24/7 support is available if needed!

Ahorre tiempo, costos y maximice el rendimiento del sitio con:

  • Instant support from WordPress alojamiento experts, 24/7.
  • Cloudflare enterprise integration.
  • Alcance of global audience with 35 data centers all over the world.
  • Optimización con nuestro monitoreo de rendimiento de applications integrado.

Todo eso y mucho más, en un solo plan sin contratos a largo plazo, migraciones asistidas y una garantía de devolución de dinero de 30 días. Consult nostros planes o hable con ventas para encontrar el plan adecuado para usted.


Video Mamp apache server won t start

Related Posts

Free chat room code for my website

Contents1 How to set up a free chat room on the website.2 3 comentarios2.1 Trackbacks/Pingbacks2.2 Submit a Comment Cancel reply3 How to Create a Chat Room Website…

Background image full screen css

Contents1 Cómo – Full Page Image1.1 Example1.2 Example2 CSS background image tamaño tutorial: how to codify a complete page background image3 Perfect Full Page Background Image3.1 Méthode CSS géniale,…

WordPress leverage browser caching

Contents1 Aproveche el almacenamiento in hidden del navegador1.1 Will it works for my website?1.2 Where are plugin options1.3 Some JavaScript files still display under Leverage Browser Caching1.4…

WordPress post to facebook page

Contents1 How to Automatically Post to Facebook from WordPress1.1 Download Now: How to Launch a WordPress Website [Free Guide + Checklist]1.2 1. Create an IFTTT account.1.3 2….

Download images from wordpress media library

Contents1 How to export your WordPress media library1.1 Download maintenant : How to launch a WordPress website [Free Guide + Checklist]1.2 How to export your WordPress media…

WordPress single post template

Contents1 How to Create Custom Unique Post Templates in WordPress2 Post Template Files2.1 author.php2.2 Fecha.php3 Handbook navigation4 How to Create Custom Single Post Templates in WordPress5 Video…