Ok. I figured out why it was going to the /index.html, but now I have a
I had a Redirect statement in my virtualhost config so that whenever
someone went to http://rt3.domain.com/ it would send them to
http://rt3.domain.com/index.html, because apache was not doing it by
default, even with the DirectoryIndex index.html statement there.
So I remove that Redirect rule, and make the users go to
http://rt3.domain.com/index.html to log in. But now when I click on the
configure link, it sends me to http://rt3.domain.com/Admin/ and of
course, I have that same problem where index.html is not assumed, so it
does not load the page. If I type in
http://rt3.domain.com/Admin/index.html it works fine.
Why isn’t apache looking for index.html by default for this virtualhost?
I do have the DirectoryIndex index.html index.htm index.cgi index.php
index.var statement elsewhere in my apache config.
Here is my virtualhost config.
I am running apache 2.0.46 on a RedHat ES3 server.
From: Nathan Tallack
Sent: Monday, 2 August 2004 8:06 AM
Subject: RT-3.2.1 Problem - Can not go into Configuration page.
I just did what seemed to be a perfectly flawless upgrade from RT2 to
Everything went smoothly. I used the RT2-3 conversion perl scripts to
dump the RT2 database out and reimport it to RT3.
I did a fresh install of RT3.2.1 onto another box, so that is where I
imported it to. The fresh install went great, and everything looks
perfect after the import. All my tickets and users are there.
Only there is one MAJOR problem. No user, not even “root” or any other
"super users" can bring up the site’s configuration page
http://rt3.domain.com/Admin when they click on the Configuration link on
the left hand menu pane.
All that happens is you get a brief pause for a few seconds, then you
get the same index.html page back.
All my perl dependencies are met. Everything installed FLAWLESSLY.
Nothing is showing up in apache’s error_log. There are no files created
in the /opt/rt3/var/log/ directory. NOTHING!!!
Anyone have any idea’s?
Thanks for your time.