AIM Not Working with Proposed Workaround
Ken Sande
sandekt at wow-ia.net
Thu Feb 18 15:19:51 EST 2010
Scott Norman wrote:
> I started receiving the following error message during the afternoon
> yesterday: Received unexpected response from
> http://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not allowed
> for non secure requests.
>
> The Pidgin website suggests to uncheck the 'Use Client Login' on the
> advanced tab of Account Settings. Now it appears that the client is
> trying to sign in but the connection isn't made. There are no error
> messages, but I also can't get signed in. I've restarted the client and
> rebooted but had not success.
>
> Thanks,
>
> Scott
>
> On Thu, Feb 18, 2010 at 11:35 AM, Evan Platt <evan at espphotography.com
> <mailto:evan at espphotography.com>> wrote:
>
> Rather than us guessing what 'error message for AIM' you are getting
> and guessing what 'suggested approach' you used (as there've been a
> few suggested fixes', what exact error message are you getting, and
> what did you do to attempt to fix it?
>
>
> On 2/18/2010 11:32 AM, Scott Norman wrote:
>
> I have applied the suggested approach for dealing with the error
> message
> for AIM and am still unable to sign in to AIM. I have the latest
> version of Pidgin as well. Please advise.
>
I saw a few emails in recent history that suggest unchecking "Use SSL"
instead of "Use ClientLogin". Seemed to work for a few people. Have you
tried that?
--
73,
Ken Sande/KC8QNI-T
More information about the Support
mailing list