[commits] [Wiki] changed: FAQ/Admin/Troubleshoot
Wiki Guest
wikiguest at horde.org
Wed Jun 12 17:35:59 UTC 2013
guest [184.144.132.184] Wed, 12 Jun 2013 17:35:59 +0000
Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision: 77
Change log: Adding error wording to ease finding solution.
@@ -21,9 +21,9 @@
: 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?". 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?". 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.
: 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.
More information about the commits
mailing list