Content
OP 3.0: directory structure instead of website after installation
Added by Fritz Müller over 10 years ago
Hello,
I am new to Openproject and ruby. Nontheless I installed Openproject 3.0 using instruction for Debian + Apache + MySQL. Installation went quite well. Just installing rvm I did being root. But user openproject could proceed further installation without flaws.
Also I wanted to integrate OP in my already existing website and not use a completely new one. So I changed /etc/apache2/conf/openproject.conf appropriately (I hope so):
Alias /openproject /home/openproject/openproject
<Directory /home/openproject/openproject/public>
- This relaxes Apache security settings.
AllowOverride all- MultiViews must be turned off.
Options -MultiViews
Now I am ready, everything seems in place. But when I open www.my-site.org/openproject I see the directory structure of “Index of /openproject” as in file:///home/openproject/openproject. No website, just file and directory names.
Donn’t know what went wrong. Any help is appreciated.
Regards,
Fritz
EDIT: Just changed the first line to
Alias /openproject /home/openproject/openproject/public
This results in an 403 error:
Forbidden
You don’t have permission to access /openproject/ on this server.
I am stuck.
Fritz
Replies (4)
Hi Fritz,
I hit the same problem with a fresh install on Debian 7.
Were you able to find the problem?
Thanks
Laurent
Ping.
No clues?
Absolutley rare phenomenon?
Never happened before?(well: once - Thank you Laurent)
Hi folks,
I went through the installation instructions once more (third time meanwhile). I noticed an error in the apache2 configuration. After correcting this and adding things according to [[https://www.openproject.org/topics/1340]] (thanks for that!) got all fixed. So it was - as often - a tiny little misspelling in the config files.
Yours humbly,
Fritz
Hi, I am having the same problem as the OP. I added the
rails_relative_url_root
toconfig/configuration.yml
and re-runRAILS_ENV="production" bundle exec rake assets:precompile
, but get 403. Fritz, what was the error in apach2 config that you fixed? Thanks!