cocoaforge

Hi,

just installed 1.4.2 and can't connect to AIM account when I am in office, here is the error:

Error: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL Connection Failed

Version 1.4.1 works OK for me.

For what it's worth: when I tried 1.4.2 this morning at home, it was connecting OK from the same MacBook. The difference is that office network is behind proxy and I guess there are some significant changes in the way it connects to AOL network, however, version 1.4.1 is still able to find the way out. Proxy settings were not changed after I installed 1.4.2, and proxy is not set in Adium, actually.

Does your work proxy (for some ridiculous/insane reason) prevent outgoing access using SSL?

zac wrote:Does your work proxy (for some ridiculous/insane reason) prevent outgoing access using SSL?

No, I don't think so. Any HTTPS connections are established just fine in a browser, at least.

Can you navigate to the above URL without suffering an SSL error? Perhaps it's the certificate.

zac wrote:Can you navigate to the above URL without suffering an SSL error? Perhaps it's the certificate.

Yes, and here is the result I saw in a browser:
statusCode=405&statusText=Method+not+allowed-+POST+method+required

I came here to look into the same issue. Adium was working fine at my work location until the 1.4.2 update.

I have found that AIM to Cellular text messaging has been broken by 1.4.2

back to iChat :-(

One more connection error, this time for mac.com account (and on home machine, where there is no proxy server):

Received unexpected response from https://api.oscar.aol.com/aim/startOSCARSession: Invalid Request. statusDetailCode 1010

Restored connectivity by re-installing an earlier version. At least it works.

I have the same error since upgrading to 1.4.2. Previous versions worked fine. I am behind a proxy server at the office and get this error for AIM accounts:
Error: Error requesting https://api.screenname.aol.com/auth/clientLogin: Error reading from api.screenname.aol.com: Unknown error: 0

Our company is using an untrusted, self-signed certificate. Going to the URL directly results in the untrusted certificate warning.

Yahoo and Google accounts work fine.
I'll check from home this evening to see if connection to AIM accounts work from outside the company proxy server/self-signed certificate.

Temporarily trusted the self-signed certificate from the office and still couldn't connect.

AIM accounts work fine from home without a proxy server in between.

Looks like many of us will have to downgrade to 1.4.1 until this issue gets resolved.

I too had to downgrade to 1.4.1 because I could not text to cel phone AND my online contacts list was acting as though they were offline. This is occurring for me at home.