Content
[SOLVED] No matching DirectoryIndex
Added by Brad Smith about 10 years ago
Hello all,
I followed the Ubuntu installation instructions and got OP installed so that it works on port 3000 under the rails server.
For a more permanent solution, I want to run it with Apache, so I used the Apache+Passenger instructions to set that up. Everything seems to work (for example, if I change the path used with any of the Passenger-related Apache directives it fails the configtest, so I know they’re being read and seem to be sane.
However, when I try to access OP, I get a 403 error in my browser, and Apache’s error log shows (substituting a simpler path than what I’m actually using):
[Fri Oct 03 20:52:19.541854 2014] [autoindex:error] [pid 25500] [client 172.19.57.108:54878] AH01276: Cannot serve directory /path/to/openproject/public/: No matching DirectoryIndex (index.htm,index.html,index.php) found, and server-generated directory index forbidden by Options directive
Indeed, OP’s public/ directory looks pretty sparse:
$ ls public/ 404.html 422.html 500.html assets favicon.ico javascripts
If I turn on +Indexes
, it lists those files, so I think the directory permissions are OK.
The one place where my configuration differs significantly from the one in the instructions is that I want to access OP as a subdirectory of an existing vhost, so my Apache config looks something like this (in my vhost’s .conf file):
LoadModule passenger_module /path/to/openproject/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.53/buildout/apache2/mod_passenger.so <IfModule mod_passenger.c> PassengerRoot /path/to/openproject/.rvm/gems/ruby-2.1.0/gems/passenger-4.0.53 PassengerDefaultRuby /path/to/openproject/.rvm/gems/ruby-2.1.0/wrappers/ruby Alias /openproject "/path/to/openproject/openproject-git/public/" <Directory /path/to/openproject/openproject-git/public/> Options -MultiViews Require all granted </Directory> </IfModule>
Does anyone have any guesses what could be going wrong here?
Replies (2)
Progress! These instructions explain what I was missing to set up an instance under a suburi of an existing vhost.
Unfortunately I’m not quite set up yet. The default un/pw for the admin doesn’t work. The instructions I’ve read are a bit unclear as to whether this should be already done for production, of if that’s only in the dev environment. In any case, I can’t find anything about how to create an admin account yourself, so any help there would be appreciated. In the mean time, I’ll keep searching…
Oookay. I think I’ve got it now. I’m certain I’d done it before, but I re-ran the db create/seed/migrate commands after getting Passenger working, and I now have an admin account!
Marking this as [SOLVED]. Hopefully if anyone else runs into this issue it’ll be of use.