Error Directory index forbidden by Options directive:

Question

Error Directory index forbidden by Options directive:

Navigation

#1 by (0 votes)
#2 by (0 votes)

1

Q Someone could help me with the following error I get when someone tries to access certain link from my site:

Directory index forbidden by Options directive:

Here is my configuration of Apache in Centos 7. I use a virtual host:

<VirtualHost *:80>
    ServerName servidor.midominio.com
    DocumentRoot /var/www/servidor/public_html

    <Directory /var/www/servidor/public_html/>
        Options -Indexes +FollowSymLinks
        AllowOverride All
        Require all granted
    </Directory>

    ErrorLog /var/www/editor/error.log
    CustomLog /var/www/editor/requests.log combined
</VirtualHost>

apache virtualhost httpd

asked by Dennis Isaias Cervantes Nuñez 05.09.2017 в 17:15

source

2 answers

Is it possible to pass parameters to a controller using the angularjs directive? Group record by column including NULL values

score 0 · Answer 1

0

Try this and restart the apache service.

<Directory /var/www/servidor/public_html/>
    Options Indexes FollowSymLinks #se quita el -
    AllowOverride All
    Require all granted
</Directory>

answered by 19.09.2017 в 23:19

score 0 · Answer 2

I had the same problem, I tried several things that I read in various parts of help and all pointed to the same thing: that if more, that if less, than if FollowSymLinks ... all aiming to modify the httpd.conf.

I guess the problem in my case was with the installation in the opensuse because in the lubuntu I had no problem making pages for the intranet. I guess my problem is trying to install things the same way as in lubuntu.

I installed Apache and those things from the console but ... well, so as not to go around so much, what I did was the following:

In opensuse you open the yast,

click on "install uninstall software",

click on see,

click on patterns,

click on "web server and LAMP", and

uninstall everything in this section (dependencies and everything),

reinstall the yast. In the console you run

zypper install yast2*"

(the asterisk is very important) and you give the fret to the dependencies, and

install Python,

then restart, and

you open the YaST

click on "install uninstall software",

then see,

click on patterns,

then palomeas "Web server and LAMP"

and click on accept.

It has worked for me in this way, I hope it will be useful, in the end the configuration remains with a none. Maybe not solve all the problem but I think that in my case is a problem with the installer, more specifically I suspect that it is a problem with the yast, so I better reinstall and I left with dependency problems that will then give me pain of head.