[cvs] [Wiki] changed: FAQ/Admin/Troubleshoot

[Jan Schneider]

jan  Wed, 01 Nov 2006 10:12:07 -0800

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision:  6.20
Change log:  Cookie problems

@@ -11,8 +11,18 @@
  
  Possible reasons could be a fatal PHP error, not being displayed to the browser (which is a good thing on production systems, but bad if you are trying to hunt down a problem)[http://www.php.net/manual/en/ref.errorfunc.php#ini.display-errors], or a segfaulting server process (happens most times in the [http://www.php.net/manual/en/ref.imap.php c-client library] while using IMP). If you correctly configured your web server and PHP to log all errors, you should find more information in your web server's or PHP's log files, or whereever you log the errors (syslog etc.).
  
  Another place to see is the Horde log which is being configured in Horde's setup. By default Horde is logging to the file /tmp/horde.log.
+
++++ After logging in users are immediately thrown back to the login screen
+If looking at the Horde log file you see a successful login attempt, and the login screen doesn't contain any error message.
+
+This happens if sessions aren't working properly for some reason. These are possible troubleshooting steps and their solutions:
+
+: Check that PHP sessions are working at all using the sessions test on the {{/horde/test.php}} test script. : Make sure that your browser accepts cookies. Otherwise check http://www.php.net/manual/en/ref.session.php for more information.
+: Try logging in with the default PHP session handler if you configured a custom session handler in Horde's setup. : If this works, something is broken with your custom session handler setup or backend. Continue troubleshooting there.
+: If using Horde 3.1.2 change the configuration to allow non-cookie, url-based sessions. : If this works, cookies aren't stored in your browser. This could be caused by the browser configuration or a faulty session cookie setup, see the next point.
+: Make sure that you are using the correct cookie domain and path settings in Horde's setup. : Cookies are not stored in the browser if you don't use a FQDN (fully qualified domain name), e.g. ``http://localhost/horde/``, or if the specified cookie path ({{/horde}} by default) doesn't match the webroot of your Horde installation, e.g. ``http://webmail.example.org``, ``http://www.example.org/horde-3.1.2``.
  
  ++ Common error messages
  See [http://wiki.horde.org/FAQ/Admin/Troubleshoot#wsod A blank white screen appears]