Question

I have been hosting a wiki for a couple of years now for friends and family. I recently upgraded my linux box to RH8.0 and thus Apache 2. The .htaccess mechanism no longer works, when I attempt to edit a page I recieve the following error..

Authorization Required This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

I am using the same .htaccess and .htpasswd files I was using with the previous version of apache, which I am assuming is my problem, any help would be appreciated.

Thanks in advance.

• TWiki version:
• Web server: x86
• Server OS: RH8
• Web browser: IE 6
• Client OS: w2k

-- KennyVoorhees - 16 Oct 2002

Related: FailedAuthenticationWithApache2OnWinNT

-- PeterThoeny - 17 Oct 2002

I cannot answer the issue of an upgrade from Apache 1.3 to Apache 2.0, but I will note that I installed TWiki on a RedHat 9 system with Apache 2.0.40 and authentication does work. That isn't to say that everything works, though. I've had very slow response times when trying to save edits to topics (5-10 minutes) and lately have had downright failures. The TWiki scripts seem to get stuck during writes. Unfortunately, I just don't know enough about how to debug the Apache/Perl combination to make much progress on this issue. If anyone has pointers, I'd love to hear them...

-- DavidBright - 06 Aug 2003

Answer

Please post a new question as mentioned in SupportGuidelines (you can paste in the text from here), with all the details including testenv output - by commenting to an existing ClosedUnanswered question you are making it very likely that you won't get an answer....

That sounds like a non-TWiki problem - try running the top command in one window while this is going on to see if there is a CPU-hogging process around. Also, check the network lights and do frequent netstat commands to see if there is a lot of DNS lookup activity. It's possible that misconfigured /etc/resolv.conf or other DNS problems are causing a large number of timeouts. TWikiDebugging may help prove whether TWiki is or is not involved in this. Even on a slow system, TWiki should handle typical transactions in less than 10 seconds.

-- RichardDonkin - 08 Aug 2003