Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Calendar Script CommunityEverything ElseGeneral Use (Moderators: scott, DanO, Marty)Login problem after server change
Pages: [1]   Go Down
Print
Author Topic: Login problem after server change  (Read 274 times)
0 Members and 1 Guest are viewing this topic.
CWwebmaster
New Member
*

Karma: 0
Offline Offline

Posts: 0

retired


WWW
« on: January 14, 2004, 08:12:00 PM »

Our Web hosting company recently moved us to a new server.  At first we could not even view the calendar.  I changed the permissions and put a check in all boxes.  Then we could see the calendar and I thought everything was just fine.  When I attempted to Login I received the following error message.

"Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request...."

Did I set the permissions incorrectly?  Or, what part of the login file (or any other file in the package) might be corrupted?

I'm using Dreamweaver on a Windows XP pro OS.  Our Web host uses a UNIX server.


Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #1 on: January 15, 2004, 01:53:00 PM »

** I changed the permissions and put a check in all boxes. **

That would make permissions set to 777 and not all host allow files or directories to be set like that for security reasons.

Normally scripts and their directories should be chmod to 755 or 775 depending... Data files and their directories to 666 or 766 depending... Check your host's CGI FAQs or ask their support what are acceptable permissions.

Dan O.

------------------

Logged
CWwebmaster
New Member
*

Karma: 0
Offline Offline

Posts: 0

retired


WWW
« Reply #2 on: January 16, 2004, 12:59:00 PM »

Thank you, Dan for your quick response.  Mark this case closed.  By using the script debugger supplied with the program, I was able to remedy my problems.
Very stupid on my part to not use this debugger sooner. Maybe this will serve as a lesson to others.

Turns out that, although I corrected the permissions on all of the files, I did not correct them for all of the directories (folders) involved.  The debugger script clearly identified the errors.

------------------

Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #3 on: January 16, 2004, 01:26:00 PM »

Glad to hear you figured it out.

Dan O.

------------------

Logged
Pages: [1]   Go Up
Print
Jump to: