For example, if you try to start Apache by using the Services applet in the Windows Control Panel, you may get the following message:. Could not start the Apache2. You will get this generic error if there is any problem with starting the Apache service.
In order to see what is really causing the problem you should follow the instructions for Running Apache for Windows from the Command Prompt. If you are having problems with the service, it is suggested you follow the instructions below to try starting httpd. Running Apache as a service is usually the recommended way to use it, but it is sometimes easier to work from the command line, especially during initial configuration and testing.
This will open a console window and start Apache inside it. If you don't have Apache installed as a service, the window will remain visible until you stop Apache by pressing Control-C in the console window where Apache is running in.
The server will exit in a few seconds. However, if you do have Apache installed as a service, the shortcut starts the service. If the Apache service is running already, the shortcut doesn't do anything. If Apache is running as a service, you can tell it to stop by opening another console window and entering:. Running as a service should be preferred over running in a console window because this lets Apache end any current operations and clean up gracefully.
But if the server is running in a console window, you can only stop it by pressing Control-C in the same window. You can also tell Apache to restart. This forces it to reread the configuration file.
Any operations in progress are allowed to complete without interruption. To restart Apache, either press Control-Break in the console window you used for starting Apache, or enter. Change to the folder to which you installed Apache, type the command httpd. Then change to the logs folder, and review the error. When working with Apache it is important to know how it will find the configuration file. You can specify a configuration file on the command line in two ways:. In both of these cases, the proper ServerRoot should be set in the configuration file.
This built-in path is relative to the installation directory. Apache will then try to determine its ServerRoot by trying the following, in this order:. If you did not do a binary install, Apache will in some scenarios complain about the missing registry key. This warning can be ignored if the server was otherwise able to find its configuration file. The value of this key is the ServerRoot directory which contains the conf subdirectory.
When Apache starts it reads the httpd. If this file contains a ServerRoot directive which contains a different directory from the one obtained from the registry key above, Apache will forget the registry key and use the directory from the configuration file.
If you copy the Apache directory or configuration files to a new location it is vital that you update the ServerRoot directive in the httpd. After starting Apache either in a console window or as a service it will be listening on port 80 unless you changed the Listen directive in the configuration files or installed Apache only for the current user.
To connect to the server and access the default page, launch a browser and enter this URL:. Apache should respond with a welcome page and you should see "It Works! If nothing happens or you get an error, look in the error. If you happen to be running Apache on an alternate port, you need to explicitly put that in the URL:. Once your basic installation is working, you should configure it properly by editing the files in the conf subdirectory. Again, if you change the configuration of the Windows NT service for Apache, first attempt to start it from the command line to make sure that the service starts with no errors.
These conflicting services include other WWW servers, some firewall implementations, and even some client applications such as Skype which will use port 80 to attempt to bypass firewall issues. Mapped drive letters allow the administrator to maintain the mapping to a specific machine and path outside of the Apache httpd configuration. However, these mappings are associated only with interactive sessions and are not directly available to Apache httpd when it is started as a service.
Skip to steps Before you begin The installation is in four parts 1 Copy the certificate files to your server 2 Configure the Apache server to point to certificate files 3 Test the configuration was successful 4 Restart the Apache server Part 1 of 4: Copy the certificate files to your server 1.
Download the certificate files. You will obtain a. Part 2 of 4: Configure the Apache server to point to the certificate files 1. Note that Vista users must turn off User Account Control in order to save the new configuration files.
In the httpd. If you have any questions or concerns please contact the Entrust Certificate Services support department for further assistance. This prevents you from being able to create the. To fix this problem, you will need to import the certificate to the same machine where the certificate's CSR was created. See Export Prerequisite. In the File name box, click … to browse the location where you want to save your files.
In the Save As window, browse for and select the location where you want to save your. Provide a file name i. After you receive the "Your certificate and key have been successfully exported" message, click OK.
0コメント