Ошибка xampp не запускается apache

После установки панели управления XAMPP в Windows 10 многие пользователи сообщали об ошибке при запуске Apache . Эта проблема обычно возникает, когда такой процесс, как World Wide Publishing Service, продолжает работать на 80-м порту вашего устройства. Из-за этого операционная система Windows 10 не позволяет серверу Apache работать, и это вызывает ошибку.

5:38:38 PM  [Apache]    Error: Apache shutdown unexpectedly.
5:38:38 PM  [Apache]    This may be due to a blocked port, missing dependencies, 
5:38:38 PM  [Apache]    improper privileges, a crash, or a shutdown by another method.
5:38:38 PM  [Apache]    Press the Logs button to view error logs and check
5:38:38 PM  [Apache]    the Windows Event Viewer for more clues
5:38:38 PM  [Apache]    If you need more help, copy and post this
5:38:38 PM  [Apache]    entire log window on the forums

Фактически, порт 80 на компьютере также был портом TCP / IP по умолчанию, который модуль Apache использует на XAMPP. А поскольку два разных приложения не могут использовать один и тот же сетевой порт, вам необходимо остановить его перед запуском сервера Apache XAMPP. Если вы также столкнулись с этой проблемой на своем устройстве, есть несколько простых способов, которые я упомянул в этом руководстве. Итак, начнем.

Очистка службы публикации в World Wide Web была бы лучшим подходом, чтобы снова запустить Apache. Однако вы также можете получить его, изменив номер порта TCP / IP или остановив службу, если это необходимо. Итак, чтобы исправить запуск Apache на панели управления XAMPP, выполните следующие возможные действия:

1. Clear World Wide Web Services
2. Изменить порт Apache TCP/IP по умолчанию
3. Остановите World Wide Web Publishing Service

Давайте посмотрим на них подробно.

1] Clear World Wide Web Services

Чтобы решить начальную проблему службы Apache, вам необходимо очистить всемирную паутину от вашего устройства. Но прежде чем начать, убедитесь, что у вас нет приложений, использующих этот сервис.

Если все в порядке, откройте панель управления в вашей системе Windows.

После того, как он откроется, выберите для просмотра панели управления параметр «Большие значки» или «Маленькие значки», чтобы можно было видеть все элементы панели управления.

Из доступных элементов выберите Программы и компоненты.

В левой боковой панели есть ссылка «Включение или отключение функций Windows», нажмите на нее.

В диалоговом окне «Функции Windows» разверните Информационные службы Интернета.

Теперь снимите флажок «World Wide Web Services» и нажмите кнопку «ОК», чтобы сохранить изменения.

Выполнив вышеуказанные действия, перезагрузите устройство. После этого откройте панель управления XAMPP и нажмите кнопку «Пуск» в Apache. Теперь он должен работать в порту 80 на вашем компьютере.

2] Изменить порт Apache TCP/IP по умолчанию

Если по какой-либо причине вышеуказанный обходной путь не работает для вас, вам необходимо настроить Apache для выполнения на другом порту TCP/IP. Итак, следуйте этим советам:

Откройте панель управления XAMPP на вашем устройстве Windows.

Нажмите на кнопку Config модуля Apache.

Выберите пункт Apache (httpd.conf) в списке всплывающего меню.

На следующей странице блокнота вам нужно найти Listen 80.

Чтобы упростить поиск, нажмите сочетание клавиш Ctrl + F. Во всплывающем меню введите то, что вы хотите найти. Марк Wrap вокруг флажка, оставить дело Match бесконтрольно, а затем нажмите на Find Next кнопку.

Как только вы найдете соответствующую строку, измените номер порта на любой произвольный номер по вашему выбору.

Например, вы можете попробовать порт 121. Тогда соответствующий результат для номера порта TCP/IP будет что-то вроде — Listen 121.

Нажмите сочетание клавиш Ctrl + S, чтобы сохранить изменения в блокноте.

Примечание. Обратите внимание, что при использовании этой конфигурации вам всегда нужно добавить номер порта TCP/IP в URL, который вы хотите подключить к своему сайту. Например, чтобы получить доступ к серверу Apache в вашем браузере, вам нужно будет ввести: localhost:121/dashboard, а не localhost/dashboard.

После правильного выполнения вышеуказанных шагов, проблема запуска Apache в XAMPP будет исправлена.

3] Остановите издательский сервис World Wide Web

В качестве альтернативы вам необходимо остановить службу публикации в Интернете и изменить ее параметры, чтобы она могла быть запущена только вручную. Итак, начнем:

Чтобы остановить службу публикации в Интернете, сначала необходимо открыть диспетчер служб Windows на компьютере с Windows 10.

На экране «Службы» найдите параметр «Служба публикации в Интернете» в столбце «Имя».

Как только вы найдете, дважды щелкните по нему, чтобы открыть окно свойств.

В окне свойств по умолчанию открывается вкладка Общие.

На вкладке General найдите тип запуска и переключите его на Manual. Это позволит вам запустить службу вручную, когда это потребуется.

Продвигаясь вперед, остановите статус работающей службы и нажмите Apply > кнопку OK.

Теперь откройте панель управления XAMPP и нажмите кнопку «Пуск», чтобы запустить сервер Apache.

Вот и все. Я надеюсь, что это руководство поможет вам исправить проблему запуска службы Apache на панели управления XAMPP.

There are many possible answers for this problem. The most common and most likely is that you’re running another program which is blocking port 80 or 443. If you’ve installed Skype, then you’ve found your problem! Change apache’s port settings to 81 and apache will work. There’s a good tutorial on that To check this you can open up your command line by clicking the start menu, and typing ‘cmd’, and enter the command

    netstat -nab

this wil return a list of programs that will vaguely resemble this pattern

    [someprogram.exe]
    UDP     [fe80::numbers:numbers:numbers:numbers%numbers]:portnumber

You need to find a line (or lines) ending in :80 and terminate them in order to start apache. If there is no line ending in :80, there are more things you can do.

First, navigate to xampp’s directory (default is c:xampp) and double click apache_start.bat. This will open up a comand line and return more detailed errors about why apache can’t run. Mostly, be looking for syntax errors that you could’ve created by editing your httpd.conf, or httpd-ssl.conf files. This is very easy to do if you’ve edited it and are a new user.

If still this fails, your last hope is to check the apache error log by clicking on the logs tab in apache’s row in the xampp control panel and clicking error log.

If none of this works, don’t give up! You got this!

Edit: If you change the port of apache, you will also have to go into httpd.conf (located in xampp/apache/conf) and near line 184, replace

ServerName localhost:80

with

ServerName localhost:81

It is also possible to specify port 81 in the url of your localhost, i.e.

localhost:81/my_project.php

XAMPP is a useful platform for WordPress developers who are looking for a localhost solution. However, some issues can show up when you’re using this tool. These errors could stall your workflow and leave you unsure how to get XAMPP running again, especially because everything may appear to be in order on the surface.

Fortunately, once you identify the reason XAMPP is not starting for you, it often takes just a few tweaks to fix it. You can then get right back to work on your latest development project.

In this article, we’ll provide a brief overview of what XAMPP is for those who are new to the platform. Then we’ll show you how to check your error logs and resolve three common problems that may keep your local server from starting. Let’s dive in!

A Brief Introduction to XAMPP

XAMPP is a free local development tool. It essentially functions as a server on your computer that you can use to host websites — much like DevKinsta, our own free local development app.

Note that these sites are not publicly available to users on the open Internet. Rather, they’re meant to be used locally for development and testing purposes. If you wish, you can migrate each project to a live server once it’s finished.

XAMPP is a handy solution because it prevents visitors from finding your project while it’s still in progress. Plus, since the site is hosted on your computer, its performance should top-notch and you can work offline.

You can use XAMPP on any major Operating System (OS), including Windows, macOS, and Ubuntu Linux. It uses the open source Apache server and MySQL, and comes with several built-in tools such as phpMyAdmin and FileZilla.

When it comes to WordPress in particular, XAMPP is one of the top localhost solutions because it meets all of the Content Management System’s (CMS’s) requirements. These include:

• PHP 7.4
• MySQL 5.6
• HTTPS support
• Apache or NGINX server

If you’re interested in installing XAMPP, you can check out our tutorial on installing WordPress locally, which includes directions for this task.

How to Check Your XAMPP PHP Error Log

In the event that you’re developing a WordPress site locally using XAMPP, and you can’t get the platform to start up, your first step should be to check your error logs. This may point you in the direction of the problem’s cause.

If you know why the issue is occurring, you should be able to resolve it much faster than troubleshooting it by trial and error. Logs are accessed using different paths, depending on your OS and version. Fortunately, there’s a simple way to find the path for your setup.

On Windows, the XAMPP activity log appears in the lower half of the control panel dialog box. You can also access the error log by by clicking on the Logs button next to the Apache Config button:

On macOS, click on the Log tab in the control panel to see the activity log:

You can then take a look through your logs to see if there’s anything suspicious and follow any directives provided to resolve the issue(s).

In some cases it may be beneficial to have access to your PHP log as well, although this is usually more helpful for troubleshooting WordPress errors than those for Apache or MySQL.

To locate your PHP error logs, open the XAMPP dashboard by typing http://localhost into your browser’s address bar. There, click PHPInfo at the top of the screen:

Then search for “error_log”. This will reveal the path you need to enter in your address bar to view the log:

You should be able to simply type this path into your browser after http://localhost to view the PHP log.

Accessing Your XAMPP-VM for Mac PHP Logs

There are actually two versions of XAMPP for Mac users – “XAMPP for macOS” and “XAMPP-VM“. The latter enables you to run XAMPP for Linux on your Mac, using a virtual machine.

It’s important to know which version you’re using because it determines how you access key files we’ll be referencing throughout this post. For instance, if you’re using XAMPP for OS X, you can simply open Finder, go to Applications > XAMPP, and look for the logs folder to find your PHP log.

However, if you’re using XAMPP-VM, you first need to open the XAMPP control panel, click on the Volumes tab, and select Mount:

Then, when you launch Finder, click on your IP address in the left-hand menu and open the lampp folder. This is where you’ll find all your XAMPP files, including your PHP error logs.

How to Fix XAMPP If It’s Not Working (3 Common Solutions)

If your error logs are not forthcoming about the cause of the problem, you can try these solutions to get XAMPP working again. These tips also elaborate on some of the instructions your error log may be showing.

1. Resolve Apache Port Conflicts

If Apache cannot start, you won’t be able to access your XAMPP dashboard or any sites you have installed on the platform. A port conflict may be the underlying problem.

By default, Apache connects over port 80. If you see an error message that says this port is already in use, another application is blocking the connection (Skype is a frequent offender).

If you click on the Netstat button in the XAMPP control panel, it should show you all the ports that are currently in use, and which applications are using them. You may want to check this if XAMPP Apache is not starting:

If you know which program is the problem and can unblock the port by removing the application that’s in the way, this will solve the issue immediately. However, you can also change the Apache listening port for XAMPP, so that you connect while leaving your other platforms intact.

First, you’ll need to find your httpd.conf file. This process is slightly different depending on your OS and which version of XAMPP you’re using.

Changing Your XAMPP Apache Port on Windows

On Windows, open the XAMPP control panel and click on the Config button:

Then select httpd.conf. Search in this file for the line that reads “Listen 80”, and change it to “Listen 8080”. This will enable you to connect to Apache over port 8080 instead of the default option.

You’ll also need to look for the line that reads ServerName localhost:80, and change this to ServerName localhost:8080. Save and close the file.

Then try starting Apache again. If this was your only problem, the platform should run as intended. However, note that if you have a WordPress installation hosted via XAMPP, you’ll need to find and replace all mentions of “localhost” with “localhost:8080”, including those in your database.

Changing Your XAMPP Apache Port on Mac

If you’re running XAMPP for macOS, you can find your httpd.conf file by going to Applications > XAMPP in Finder. Once you find the file, you can carry out the same steps to change your port as we described for Windows users.

For those using XAMPP-VM, scroll back up to the section where we explained how to access your error logs to learn how to find your XAMPP files. Once you access the lampp directory, you’ll find httpd.conf in apache2 > conf.

2. Include the Listening Port in the Address When Accessing Localhost

Normally, you can simply type http://localhost into your browser’s address bar to access your XAMPP-hosted sites or dashboard. The platform automatically connects to Apache over its default listening port, 80.

However, if you’ve changed your XAMPP installation’s listening port (or someone else with access to your computer did so), it won’t be able to connect. You may also see this occur if there’s an Apache port conflict, as described above.

This problem can be quite confusing because the XAMPP control panel may show that Apache and MySQL are both running. However, you won’t be able to access your site or tools such as PHPInfo or phpMyAdmin.

This error can take a few different forms. If you’re trying to access your local WordPress site, you may see a 404 error page. Chrome users may see ERR_CONNECTION_REFUSED instead:

Fortunately, the solution is fairly simple. You simply need to append the listening port to the address. For example, if you’re using the most common alternative port, you would enter http://localhost:8080 instead of just http://localhost.

However, if you would like to be able to simply enter localhost even though you have changed your Apache listening port, you can do so.

Changing the Default Port on Windows

Windows users change the XAMPP Apache default port to their new listening port so that you don’t have to specify it in the address bar. To do so, click on Config > Service and Port Settings > Apache in the XAMPP control panel:

Then replace the Main Port value with the new Apache port you configured and save your changes.

Set Up Port Forwarding on macOS

On macOS the process is quite different. In your control panel, click on the Network tab. Here you can set up port forwarding rules:

You’ll want to add a new rule that redirects traffic to the default port to your new Apache listening port. If you click on Add, you’ll be able to enter these values in the relevant fields:

Select the rule from the list and click on the Enable button to start using it.

3. Change Your MySQL Port

Finally, sometimes XAMPP is not working due to an issue with MySQL, rather than Apache. However, the problem is still often a port conflict, which means that by now you should have a good idea on how to fix it.

In this case, you’ll need to access your php.ini file instead of your configuration file. Navigating to your XAMPP dashboard and clicking on PHPInfo as we described earlier in this post will enable you to find the path to this file for your installation:

Alternatively, if you’re using XAMPP for Windows, you can access this file from the control panel by click on Config > PHP (php.ini):

Once you find and open php.ini, look for the lines that read port = 3306, and change them to read port = 3307. Save and close the file, and then restart MySQL.

Summary

XAMPP is a helpful tool to have in your corner, but it can be frustrating to troubleshoot certain errors that prevent you from accessing your local WordPress site. Fortunately, these are often port conflicts that you can quickly implement workarounds for.

In this article, we showed you what to do if XAMPP isn’t working due to a problem with Apache or MySQL:

1. Resolve Apache port conflicts by changing your listening port to 8080.
2. Include the listening port in the address when accessing localhost.
3. Change your MySQL port to 3307 if another application is blocking the default port 3306.

Don’t forget to check out DevKinsta as an alternative to XAMPP.

XAMPP is a useful platform for WordPress developers who are looking for a localhost solution. However, some issues can show up when you’re using this tool. These errors could stall your workflow and leave you unsure how to get XAMPP running again, especially because everything may appear to be in order on the surface.

Fortunately, once you identify the reason XAMPP is not starting for you, it often takes just a few tweaks to fix it. You can then get right back to work on your latest development project.

In this article, we’ll provide a brief overview of what XAMPP is for those who are new to the platform. Then we’ll show you how to check your error logs and resolve three common problems that may keep your local server from starting. Let’s dive in!

A Brief Introduction to XAMPP

XAMPP is a free local development tool. It essentially functions as a server on your computer that you can use to host websites — much like DevKinsta, our own free local development app.

Note that these sites are not publicly available to users on the open Internet. Rather, they’re meant to be used locally for development and testing purposes. If you wish, you can migrate each project to a live server once it’s finished.

XAMPP is a handy solution because it prevents visitors from finding your project while it’s still in progress. Plus, since the site is hosted on your computer, its performance should top-notch and you can work offline.

You can use XAMPP on any major Operating System (OS), including Windows, macOS, and Ubuntu Linux. It uses the open source Apache server and MySQL, and comes with several built-in tools such as phpMyAdmin and FileZilla.

When it comes to WordPress in particular, XAMPP is one of the top localhost solutions because it meets all of the Content Management System’s (CMS’s) requirements. These include:

• PHP 7.4
• MySQL 5.6
• HTTPS support
• Apache or NGINX server

If you’re interested in installing XAMPP, you can check out our tutorial on installing WordPress locally, which includes directions for this task.

How to Check Your XAMPP PHP Error Log

In the event that you’re developing a WordPress site locally using XAMPP, and you can’t get the platform to start up, your first step should be to check your error logs. This may point you in the direction of the problem’s cause.

If you know why the issue is occurring, you should be able to resolve it much faster than troubleshooting it by trial and error. Logs are accessed using different paths, depending on your OS and version. Fortunately, there’s a simple way to find the path for your setup.

On Windows, the XAMPP activity log appears in the lower half of the control panel dialog box. You can also access the error log by by clicking on the Logs button next to the Apache Config button:

On macOS, click on the Log tab in the control panel to see the activity log:

You can then take a look through your logs to see if there’s anything suspicious and follow any directives provided to resolve the issue(s).

In some cases it may be beneficial to have access to your PHP log as well, although this is usually more helpful for troubleshooting WordPress errors than those for Apache or MySQL.

To locate your PHP error logs, open the XAMPP dashboard by typing http://localhost into your browser’s address bar. There, click PHPInfo at the top of the screen:

Then search for “error_log”. This will reveal the path you need to enter in your address bar to view the log:

You should be able to simply type this path into your browser after http://localhost to view the PHP log.

Accessing Your XAMPP-VM for Mac PHP Logs

There are actually two versions of XAMPP for Mac users – “XAMPP for macOS” and “XAMPP-VM“. The latter enables you to run XAMPP for Linux on your Mac, using a virtual machine.

It’s important to know which version you’re using because it determines how you access key files we’ll be referencing throughout this post. For instance, if you’re using XAMPP for OS X, you can simply open Finder, go to Applications > XAMPP, and look for the logs folder to find your PHP log.

However, if you’re using XAMPP-VM, you first need to open the XAMPP control panel, click on the Volumes tab, and select Mount:

Then, when you launch Finder, click on your IP address in the left-hand menu and open the lampp folder. This is where you’ll find all your XAMPP files, including your PHP error logs.

How to Fix XAMPP If It’s Not Working (3 Common Solutions)

If your error logs are not forthcoming about the cause of the problem, you can try these solutions to get XAMPP working again. These tips also elaborate on some of the instructions your error log may be showing.

1. Resolve Apache Port Conflicts

If Apache cannot start, you won’t be able to access your XAMPP dashboard or any sites you have installed on the platform. A port conflict may be the underlying problem.

By default, Apache connects over port 80. If you see an error message that says this port is already in use, another application is blocking the connection (Skype is a frequent offender).

If you click on the Netstat button in the XAMPP control panel, it should show you all the ports that are currently in use, and which applications are using them. You may want to check this if XAMPP Apache is not starting:

If you know which program is the problem and can unblock the port by removing the application that’s in the way, this will solve the issue immediately. However, you can also change the Apache listening port for XAMPP, so that you connect while leaving your other platforms intact.

First, you’ll need to find your httpd.conf file. This process is slightly different depending on your OS and which version of XAMPP you’re using.

Changing Your XAMPP Apache Port on Windows

On Windows, open the XAMPP control panel and click on the Config button:

Then select httpd.conf. Search in this file for the line that reads “Listen 80”, and change it to “Listen 8080”. This will enable you to connect to Apache over port 8080 instead of the default option.

You’ll also need to look for the line that reads ServerName localhost:80, and change this to ServerName localhost:8080. Save and close the file.

Then try starting Apache again. If this was your only problem, the platform should run as intended. However, note that if you have a WordPress installation hosted via XAMPP, you’ll need to find and replace all mentions of “localhost” with “localhost:8080”, including those in your database.

Changing Your XAMPP Apache Port on Mac

If you’re running XAMPP for macOS, you can find your httpd.conf file by going to Applications > XAMPP in Finder. Once you find the file, you can carry out the same steps to change your port as we described for Windows users.

For those using XAMPP-VM, scroll back up to the section where we explained how to access your error logs to learn how to find your XAMPP files. Once you access the lampp directory, you’ll find httpd.conf in apache2 > conf.

2. Include the Listening Port in the Address When Accessing Localhost

Normally, you can simply type http://localhost into your browser’s address bar to access your XAMPP-hosted sites or dashboard. The platform automatically connects to Apache over its default listening port, 80.

However, if you’ve changed your XAMPP installation’s listening port (or someone else with access to your computer did so), it won’t be able to connect. You may also see this occur if there’s an Apache port conflict, as described above.

This problem can be quite confusing because the XAMPP control panel may show that Apache and MySQL are both running. However, you won’t be able to access your site or tools such as PHPInfo or phpMyAdmin.

This error can take a few different forms. If you’re trying to access your local WordPress site, you may see a 404 error page. Chrome users may see ERR_CONNECTION_REFUSED instead:

Fortunately, the solution is fairly simple. You simply need to append the listening port to the address. For example, if you’re using the most common alternative port, you would enter http://localhost:8080 instead of just http://localhost.

However, if you would like to be able to simply enter localhost even though you have changed your Apache listening port, you can do so.

Changing the Default Port on Windows

Windows users change the XAMPP Apache default port to their new listening port so that you don’t have to specify it in the address bar. To do so, click on Config > Service and Port Settings > Apache in the XAMPP control panel:

Then replace the Main Port value with the new Apache port you configured and save your changes.

Set Up Port Forwarding on macOS

On macOS the process is quite different. In your control panel, click on the Network tab. Here you can set up port forwarding rules:

You’ll want to add a new rule that redirects traffic to the default port to your new Apache listening port. If you click on Add, you’ll be able to enter these values in the relevant fields:

Select the rule from the list and click on the Enable button to start using it.

3. Change Your MySQL Port

Finally, sometimes XAMPP is not working due to an issue with MySQL, rather than Apache. However, the problem is still often a port conflict, which means that by now you should have a good idea on how to fix it.

In this case, you’ll need to access your php.ini file instead of your configuration file. Navigating to your XAMPP dashboard and clicking on PHPInfo as we described earlier in this post will enable you to find the path to this file for your installation:

Alternatively, if you’re using XAMPP for Windows, you can access this file from the control panel by click on Config > PHP (php.ini):

Once you find and open php.ini, look for the lines that read port = 3306, and change them to read port = 3307. Save and close the file, and then restart MySQL.

Summary

XAMPP is a helpful tool to have in your corner, but it can be frustrating to troubleshoot certain errors that prevent you from accessing your local WordPress site. Fortunately, these are often port conflicts that you can quickly implement workarounds for.

In this article, we showed you what to do if XAMPP isn’t working due to a problem with Apache or MySQL:

1. Resolve Apache port conflicts by changing your listening port to 8080.
2. Include the listening port in the address when accessing localhost.
3. Change your MySQL port to 3307 if another application is blocking the default port 3306.

Don’t forget to check out DevKinsta as an alternative to XAMPP.

XAMPP is a helpful development tool. However, you may run into problems at some point, such as receiving the notification: “Apache shutdown unexpectedly”. This error might seem to come out of nowhere, so identifying the cause – let alone the solution – can be puzzling.

Fortunately, there is a common explanation for Apache’s sudden shutdown. With a few simple modifications, you should be able to fix the problem and get Apache up and running again. All you have to do is update some settings in the configuration files.

In this article, we’ll discuss the common cause of this Apache error in XAMPP and then walk you through four steps to fix it, both on Windows and macOS.

Let’s get started!

An Introduction to the XAMPP “Apache Shutdown Unexpectedly” Error

XAMPP is a free, open source server stack that includes the Apache server and MariaDB database:

It runs PHP and Perl scripts, and is used to develop and test dynamic websites on local machines. This means that if you are building a website, you can install WordPress locally on your computer. You can use XAMPP without having to upload your site’s files to your web hosting service.

If you’re reading this article, we’ll assume you’re already at least somewhat familiar with XAMPP. However, what may be new to you is the “Apache shutdown unexpectedly” error you’re seeing.

This message is most commonly caused by a blocked port. Usually, it means that another application installed on your computer, such as Skype, is using the same port as XAMPP. Additionally, you may notice that the error message indicates the problem may also be attributed to “missing dependencies, improper privileges, a crash, or a shutdown by another method.”

In any event, the easiest fix is to simply modify the XAMPP default settings. However, the method for resolving the error varies slightly between Windows and macOS. Also, the interface may look a bit different depending on the XAMPP version you’re using. We will provide instructions for both operating systems below, starting with Windows.

How to Fix the XAMPP Error “Apache Shutdown Unexpectedly” in Windows

If you’re using a Windows device, you can follow these four steps to update your default port settings in XAMPP.

Step 1: Open the Configuration Settings from the XAMPP Control Panel

The first step is, of course, to launch XAMPP. This will open the XAMPP control panel. From here, you can update the configuration settings for the server stack.

Since this error is related to Apache, we’ll focus on those settings. In the “Apache” row of options, click on the Config button.

This will open a drop-down menu of files. We’re going to be editing two of these files, starting with httpd.conf.

Step 2: Change the Default Port Settings of the httpd.conf File

From the menu of files, click on Apache (httpd.conf). Once you do, the file will open in your computer’s default text editor:

Within this file, there are three settings you’ll want to update. To get started, press Ctrl + F, then enter “80” in the search field:

This will display all instances of the number 80 in the file. Locate “Port 80” and change it to “Port 8080”. Once the port setting is updated, search for “Listen 80” and update it to “Listen 8080”.

Finally, search for “servername localhost:80”. Once you find it, modify it to “servername localhost:8080”. When you’re finished, save and close the file.

Step 3: Update the Default Port Settings in the http-ssl.conf File

Now it’s time to move on to the second file. To do so, you can return to the XAMPP control panel, then select Config under the Apache settings again. This time, open the Apache (http-ssl.conf) file.

When the file opens in your text editor, press Ctrl + F, and then enter 443 in the search field. Locate “Listen 443” and update this to “Listen 4433”.

Next, search the file for the next instance of “443”. It should be “<VirtualHost _default_:443>”. Once you find it, you can go ahead and change it to “<VirtualHost _default_:4433>”. When you’re finished, remember to save and close the file.

Step 4: Restart Apache

Once you’ve updated the settings in both files, the final step is to stop Apache. You can do this by clicking on the Stop button along the same Apache row. After Apache has been stopped, click the Start button to complete the restart process.

That’s it! Your port numbers will be updated and Apache should now run without error.

How to Fix the XAMPP Error “Apache Shutdown Unexpectedly” in macOS

Depending on what version of macOS you’re running, you may already have Apache installed on your computer. This default application of Apache will use the same default port settings as the Apache server in XAMPP, so this may be the cause of the “Apache shutdown unexpectedly” error.

If you’re using macOS, you can follow these four steps to update the default port settings.

Step 1: Open the XAMPP Apache Configuration

To start, open the XAMPP Application Manager if you haven’t already done so:

Next, select the Manage Servers tab next to the Welcome tab at the top:

On this screen, you’ll find a list of options. You can click on Apache Web Server, followed by the Configure button.

Step 2: Open the Conf File

From the Configure Apache Web Server box, select Open Conf File:

A warning box will appear, stating that the file is for advanced users:

You can click on Yes to continue. This will open the httpd.conf file.

Step 3: Update the Port Settings

Once the file opens in your text editor, the next step is to update the port settings. To do so, you can hit Ctrl + F, and then enter “80” in the search field. This will display instances of the number 80:

Locate the these lines:

#Listen 12.34.56.78:80
Listen 80
Once you do, go ahead and change them to the following:
#Listen 12.34.56.78:8080
Listen 8080

When you’re done, you can save and close the file. In the Configure Apache Web Server box, click on OK.

Step 4: Restart Apache

The final step is to stop and restart Apache, which you can do from the XAMPP Application Manager’s Manage Servers tab. Once Apache is stopped, click on Start to restart:

That’s it! Your port numbers will be updated and Apache should now run without error.

Summary

The XAMPP error “Apache shutdown unexpectedly” is commonly caused by another program, such as Skype, using the default Apache port. While this can be frustrating, it usually has a simple resolution.

As we discussed in this article, the easiest way to fix this problem is to update XAMPP’s Apache configuration settings. You can do this by editing the httpd.conf file and the http-ssl.conf file (for Windows users). Once this is done, you should stop and restart Apache to resume normal operation.

Есть много возможных ответов на эту проблему. Наиболее распространенным и, скорее всего, является то, что у вас запущена другая программа, которая блокирует порт 80 или 443. Если вы установили Skype, вы нашли свою проблему! Измените настройки порта apache на 81, и apache будет работать. Там есть хороший учебник по этому вопросу. Чтобы проверить это, вы можете открыть свою командную строку, щелкнув меню «Пуск» и набрав «cmd», и введите команду

    netstat -nab

этот wil возвращает список программ, которые будут смутно напоминать этот шаблон

    [someprogram.exe]
    UDP     [fe80::numbers:numbers:numbers:numbers%numbers]:portnumber

Вам нужно найти строку (или строки), заканчивающуюся на: 80, и завершить их, чтобы запустить apache. Если строка не заканчивается на: 80, вы можете сделать больше вещей.

Сначала перейдите в каталог xampp (по умолчанию — c:xampp) и дважды щелкните apache_start.bat. Это откроет линию comand и вернет более подробные ошибки о том, почему apache не может работать. В основном, нужно искать синтаксические ошибки, которые вы могли бы создать, отредактировав файлы httpd.conf или httpd-ssl.conf. Это очень легко сделать, если вы отредактировали его и стали новым пользователем.

Если это не удается, ваша последняя надежда — проверить журнал ошибок apache, щелкнув вкладку журналов в строке apache на панели управления xampp и щелкнув журнал ошибок.

Если ничего из этого не получится, не сдавайтесь! Вы получили это!

Изменить: Если вы измените порт apache, вам также придется перейти в httpd.conf(расположенный в xampp/apache/conf) и около строки 184, замените

ServerName localhost:80

с

ServerName localhost:81

Также можно указать порт 81 в URL вашего локального хоста, т.е.

локальный: 81/my_project.php

Перейти к содержимому

Я успешно установил XAMPP (xampp-win32-1.8.2-0-VC9-installer.exe) в Windows 7. Но, к сожалению, во время запуска Apache из панели управления XAMPP была обнаружена следующая ошибка:

  netstat -nab 

  [someprogram.exe] UDP [fe80::numbers:numbers:numbers:numbers%numbers]:portnumber 

  #Listen 0.0.0.0:80 #Listen [::]:80 Listen 80 

  #Listen 0.0.0.0:81 #Listen [::]:81 Listen 81 

 Listen 80 to Listen 81 ServerName localhost:80 to ServerName localhost:81 

 Services.msc and stopped the 'Workstation' Services. 

 <VirtualHost _default_:443> DocumentRoot "D:/Server/xServer" ServerName xyz.abc.com SSLCertificateFile "conf/ssl.crt/xyz.crt" SSLCertificateKeyFile "conf/ssl.key/sftaps.in.key" </VirtualHost>