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

[Jan Schneider]

jan  Wed, 12 Jun 2013 21:54:45 +0200

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision:  78
Change log:  Move to the proper place

@@ -14,16 +14,17 @@
  Another place to see is the Horde log which is being configured in  
Horde's setup. By default Horde is logging to the syslog if using  
Horde 4 or later, resp. to the file /tmp/horde.log if using Horde 3 or  
older.

  +++ After logging in users are immediately thrown back to the login screen
  +++ The login screen keeps reloading constantly
++++ Error messages like "User is not authorized" in IMP
  If looking at the Horde log file you see a successful login attempt,  
and the login screen doesn't contain any error message, or the login  
screen keeps reloading while you are using the "Automatic"  
authentication driver, e.g. during the initial setup.

  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. : If not, make sure that your  
browser accepts cookies. Otherwise check  
http://www.php.net/manual/en/ref.session.php for more information and  
hints.
  : 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 or later, 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. If you already  
locked yourself out of Horde, edit the configuration file  
{{horde/config/conf.php}} manually and set  
{{$conf['session']['use_only_cookies'] = false;}}.
-: 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/``. To find this, go to the Horde  
configuration page on the General tab, and the last box on that page  
says "What path should we set cookies to?". Seeing the error "IMP  
"User is not authorized" " may also be an indication of this problem.   
Alternatively, in conf.php, look for the value  
$conf['cookie']['path']. Set that to the base URL for horde.
+: 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/``. To find this, go to the Horde  
configuration page on the General tab, and the last box on that page  
says "What path should we set cookies to?". Alternatively, in  
conf.php, look for the value $conf['cookie']['path']. Set that to the  
base URL for horde.
  : If session.auto_start is set to 1 in the php.ini file the login  
page will loop. : Set it to 0.
  : Delete any cookies in your browser for Horde to test any of the  
above changes. : Otherwise wrong cookies might be stored in your  
browser and the above actions still fail
  : Check the session storage. : By default sessions are stored on the  
file system, check that your hard-disc partitions still have plenty of  
room for session storage.