Usually we will encounter "you don't havepermission to access/on this server." The hint, literally, is that we don't have access to this server, so what's the common problem ?
If the first is a virtual host, then it may be a virtual host configuration error, when we configure in <VirtualHost>, in its sub-configuration, we modify in <Directory> as follows:
Order Allow,deny
Allow from all
The second reason is that we do not respond to the file name, for example, I use the Laravel framework, its entry file is server.php, not our popular sense of index.php, then when we visit the framework, we will also report similar errors, we only need to < Ifmodule dir_module> to add the corresponding files in the DirectoryIndex, here is an example:
<ifmodule dir_module>
DirectoryIndex index.html index.htm index.php server.php
</IfModule>
It is important to note that after setting up the configuration item, we also need to reboot the server. Because I use Apache here, so this is relative to Apache, for other servers, there will be similar operations.
Sinsing Analysis of You don ' t has permission to access/on the workaround for this server.