Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've recently installed Bugzilla 2.20 and for the life of me, I can't figure out why apache will not open up the index.html file located in /var/www/html/bugzilla. This directory is a symbolic link to /usr/local/bugzilla-2.20.
My etc/httpd/conf/httpd.conf file has:
DirectoryIndex index.html index.html.var index.cgi
Options Indexes FollowSymLinks +ExecCGI in the <Directory /> as well as <Directory /var/www/html>. I'm also using .htaccess files and they all are setup properly (I believe)!
I have checked the permissions of the directories in question and they are similar to a test machine I have that is hosting a working bugzilla.
What else would I need to check to ensure that this page loads up?
PS: This server is also serving as my webmail server and those pages are displaying properly!
IIRC, the documentation of bugzilla does say that in the directory directive to use +FollowSymLinks, but I can't be totally sure as when I set up bugzilla to test it, I installed the bugzilla directory directly in the document root. It still didn't work for me until i changed all the .cgi files' permissions to 755. it seemed to me that running checksetup.pl the last time really does make the files pretty restrictive. Anyhoo, I don't really know much about bugzilla, but I didn't want your post to feel lonely.
Hope you get it sorted out.
Quote:
Optional: If Bugzilla does not actually reside in the webspace directory, but instead has been symbolically linked there, you will need to add the following to the Options line of the Bugzilla <Directory> directive (the same one as in the step above):
+FollowSymLinks
Without this directive, Apache will not follow symbolic links to places outside its own directory structure, and you will be unable to run Bugzilla.
Thanks for your suggestions. However, even after making the modifications, I'm still at the same point - still getting error 404!
This one really has me stumped! I'll try and sort it out and post back here when I find a solution. Somebody elsewhere might benefit as Bugzilla traffic seems to be slow here at LinuxQuestions.
Well, turns out it was a virtualhost that was setup for webmail purpose that was killing all other requests for webpages. I finally asked myself why webmail ws as working and nothing else was being served. Then I remembered having setup the virtualhost thing (which I might add I did not understand quite well at the time).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.