Strange new login error

My SecurityAssist -generated security log in pages were working great until just now.
When I try to log in, the URL goes to
http://www.bristolcasualsleague.co.uk/login.php?accesscheck=%2Fadmin%2Fteamhome.php%3F%26accesscheck%3D%2Fadmin%2Fteamhome.php%3F%26accesscheck%3D%2Fadmin%2Fteamhome.php%3F%26accesscheck%3D%2Fadmin%2Fteamhome.php%3F.............

and recurs for about a mile!

I get a 302 error that says

Moved Temporarily

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

Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

All was well just now and it seemed to break of its own accord. I rebuilt a simple uthenticate User login and that works ok. I have rerun the SecurityAssist login pages generator again and loaded new files, but same error...

Site launch due tonight - and chance of a quick heads-up? Thanks Ray

I'd need FTP access and a username and password to test with to debug.

It might be a server issue with Session variables not storing correctly, or it could be an issue with the login rule applied on teamhome.php.

THanks Ray, Getting a lot of grief from users today so really appreciate it:

That ftp information doesn't seem to work for me. Please make sure you don't have any typos.

see pm

This was happening because you weren't storing all of the necessary Session variables when a user had selected AutoLogin.

There are two user authentication server behaviors on the page... one for auto login and one for standard login. The rule on the page /admin/teamhome.php was looking for the TeamID session variable, but that session variable wasn't being stored in the Authenticate User server behavior in the autologin case.

I fixed the problem by updating the login page so that the same session variables were stored during the form and auto login server behaviors.

Ray, if you lived in England I would give you a knighthood.
Once again, the fastest, most efficient support I have ever come across.Thank you