Because the JIRA used by the company needs a test management plug-in, but most of them are charged, and they are not generally expensive, but TestLink is adopted.
It is installed and configured with vertigoserv package, which includes Apache, MySQL and PHP. Finally, unzip the TestLink to the
It should be noted that before the installation and configuration, IIS already exists, and the site has been deployed. The 80 port used and other ports used by Apache are also normal. After using it for a long time, suddenly one morning, the vertigoserv service hangs up, and it always reports when it starts to restart
You don't have permission to access / on this server.
Check the data and modify Apache’s
http.confDocuments, as follows:
<Directory /> AllowOverride none Require all allow </Directory>
Results restart vertigoserv again, and start to report that port 80 is occupied, as shown in the following figure:
As a result, I began to search all kinds of data, and it took two hours to solve the problem. The main points of the methods are as follows:
- Modify other Apache ports (HTTP. CONF);
- Run vertrigoserv through the administrator;
- Bind the 80 port used by IIS to other ports;
- Restart the server;
But the end result is still questionable. Recall that at the beginning, it only reported 403 errors, but vertigoserv can start Apache normally, and when IIS used port 80, vertigoserv was normal. The problem should be the configuration of http.conf.
Finally, change the configuration file to:
<Directory /> AllowOverride none Require all granted </Directory>
After that, vertigoserv can start the Apache service normally and visit the site normally.
Note: run vertigoserv as an administrator and start the server.
The effects of the following parameters are summarized:
- Require all allow: Apache cannot be started, port 80 of error reporting is occupied;
- Require all denied: Apache can be started normally, with 4003 error reported;
- Require all granted: Apache can be started and accessed normally;
I hope this article will be helpful to you.
If you need to reprint, please indicate the original link: https://segmentfault.com/a/11
- The problem of 403 Forbidden in Apache httpd server