Re: Standalone Horde server access disabled overnight (wrong username or password)

Michael J Rubinsky <[email protected]> Wed, 20 Feb 2019 21:55:46 +0000
Newsgroups gmane.comp.horde.user
Message-ID <20190220215546.Horde.F42tG5XolCAOy9W1McwtkQ8@tarn.theupstairsroom.com>
Quoting Arjen de Korte <[email protected]>:

> Citeren L A <[email protected]>:
>
>> On Wed, Feb 20, 2019 at 8:44 AM L A <[email protected]> wrote:
>>
>>> Hello,
>>>
>>> I have been running Horde on a Centos VPS (located at home) for 7+years
>>> now, and it always worked great.  Yesterday I was using it without issues.
>>> It is configured to use my GMail account as auth backend.
>>>
>>> /var/www/html/horde/imp/config/backends.php has this in it:
>>> // IMAP server
>>> $servers['imap'] = array(
>>>   // ENABLED by default; will connect to IMAP port on local server
>>>   'disabled' => false,
>>>   'name' => 'GMail IMAP Server',
>>>   'hostspec' => 'imap.gmail.com',
>>>   'hordeauth' => true,
>>>   'protocol' => 'imap',
>>>   'port' => 993,
>>>   // Plaintext logins are disabled by default on IMAP servers (see RFC
>>> 3501
>>>   // [6.2.3]), so TLS is the only guaranteed authentication available by
>>>   // default.
>>>   'secure' => 'ssl',
>>> );
>>>
>>> Like I said this server has worked flawlessly for years.  This morning, I
>>> cannot login to my Horde server.  I get "Login failed because your username
>>> or password was entered incorrectly." at the login page.
>>>
>>> I have confirmed that I can login to gmail.com using the same
>>> credentials, and it works.  My android phone also works with gmail without
>>> issues.  So what happened?  Its a major issue because I am managing a condo
>>> property and use this horde install for calendar/tasks/contacts so now I'm
>>> locked out...
>>>
>>> Anybody can help?
>>>
>>
>> Geez I forgot to add the log's contents:
>>
>> Feb 20 09:25:52 centos-mail HORDE: [horde] PHP ERROR:
>> call_user_func_array() expects parameter 1 to be a valid callback, class
>> 'Horde_Deprecated' does not have a method 'verifySignedUrl' [pid 1158 on
>> line 1196 of "/usr/share/pear/Horde.php"]

The line above also leads me to suspect that you have a fairly  
outdated Horde_Core library installed.


>> Feb 20 09:25:53 centos-mail HORDE: [imp] [login] Mail server denied
>> authentication. [pid 1158 on line 730 of
>> "/var/www/html/horde/imp/lib/Imap.php"]
>> Feb 20 09:25:53 centos-mail HORDE: [imp] FAILED LOGIN for [email protected]
>> (XXX.XXX.XXX.XXX) to {imap://imap.gmail.com:993/} [pid 1158 on line 157 of
>> "/var/www/html/horde/imp/lib/Auth.php"]
>> Feb 20 09:25:53 centos-mail HORDE: [horde] FAILED LOGIN for
>> [email protected] to horde (XXX.XXX.XXX.XXX) [pid 1158 on line 199 of
>> "/var/www/html/horde/login.php"]
>>
>> Would the problem be on Google's side?  Legacy app access is enabled in my
>> google account (has always been for horde).  I have also ruled out firewall
>> issues.
>
> Fix your configuration. You should *never* modify  
> 'horde/imp/config/backends.php', only override defaults in  
> 'horde/imp/config/backends.local.php' like
>
> <?php
> $servers['imap']['name'] = 'GMail IMAP Server';
> $servers['imap']['hostspec'] = 'imap.gmail.com';
> $servers['imap']['hordeauth'] = true;
> $servers['imap']['port'] = 993;
> $servers['imap']['secure'] = 'ssl';
>
> Then enable debugging
>
> $servers['imap']['debug'] = '/tmp/imp_imap.log';
>
> The information in the logfile should provide clues why Gmail won't  
> let you in.
>
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
Horde mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]
(unnamed) (application/pgp-keys, 9.1 KB) - not displayed
signature.asc (application/pgp-signature, 821 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4

iQIcBAABAgAGBQJcbcziAAoJEJGSgkbRsxbbirEP/163DkFM9g6BYwTeh5opGDp4
rdmAjFKe/AkJJuAdtumvJxSDuhdpj1wvr5wUbFiscH7T93qKTwroa53X3MxNJwpz
BVLwowbcPdX5lduIgTimMKXDPqRuDci6D9rbOpnDKOgKr3QQ4U3BPX4KhxUxBzvj
TwYInID1cZCS+/4qaZNp6aSuM8Kgd+PSwTM0+ZwV94IIf3ZCC8DMJHQItl+tmzbB
us4RlQwkbMplpRE6VfqR9O5y4bXO/xAdRKE5k/yX0a6CdnjeFnpXdU0f0tqOqLmx
UVi45ItTpV4oVnM8BMdHFWPg9B1Zsk9RUMXyDvgV+ZUXL75kbtzazuTmmt5XMP9h
HhrIKplXRgwCGl0Es+oB1ivHFPbwFz0KuJw+1cdKnzQZJEAvAGjzHz8164cxaZeD
XPF3Oz1Ttdn5fRUFbssJAr4/mICF98Erpodz2K8ARY7jEKdLG8q9Gk6E6QtOcA1g
SKHv1wCvl5D5EyKXik1Pf8kwsA+di4JIoprbJNWUvVQ7rtq9GSZckrORtNk9xl0i
L97J2DVLKxliNL6NuLf8BQLjztXQBSTZNhgDZ3v8sycSHY/efENWXZ50bh+3f4ay
yN2yJFNggJxQtfdPtYV9uL0wNhwsFkgEI4iVJBtMMwax3TG3OhTa9QcrIzC852rd
wQ0seEdAq8l58VUr0awb
=aOBF
-----END PGP SIGNATURE-----