Opened 8 years ago

Last modified 8 years ago

#14594 new defect

Unable to authenticate on iChat through port 5223

Reported by: michael.heuberger Owned by: deryni
Milestone: Component: XMPP
Version: 2.10.0 Keywords: 5222 5223
Cc:

Description

Hi there

After my colleague has updated the iServer and changed the iChat port from 5222 to 5223 I'm unable to log in with Pidgin through the XMPP (Jabber) protocol.

Looks like Pidgin can't cope with the higher security settings. I changed the "Connection Security" under the advanced tab to "Require encryption" and set the "Connect port" to 5223. Then Pidgin tries to connect forever and forever without a timeout. No warning, no message at all.

If my colleague changes the iChat port back to 5222 and I use that port, it's working fine. But we want to chat on a secure layer and ran out of options for that riddle. Maybe you can help us or know the culprit?

Thanks Michael

Attachments (1)

debug.log (265.2 KB) - added by michael.heuberger 8 years ago.
Here, my debug log when starting Pidging and connecting to the iChat server …

Download all attachments as: .zip

Change History (6)

comment:1 Changed 8 years ago by datallah

  • Status changed from new to pending

Please follow the instructions to get a debug log and attach it to this ticket.

comment:2 Changed 8 years ago by rekkanoryo

  • Milestone 2.10.1 deleted

Port 5223 is for old-style SSL, instead of modern TLS. Setting the "Connection security" option to old-style SSL will allow you to connect. If iChat server doesn't allow upgrading to a TLS-encrypted connection via STARTTLS, then the server is broken.

Changed 8 years ago by michael.heuberger

Here, my debug log when starting Pidging and connecting to the iChat server ...

comment:3 Changed 8 years ago by michael.heuberger

  • Status changed from pending to new

Attachment (debug.log) added by ticket reporter.

comment:5 Changed 8 years ago by michael.heuberger

OK, I have attached the debug file, see attachment. I have three accounts configured, two are working fine, the one with admin.fybe.com is the problematic one (have a look from line 960 on in the debug file)

@rekkanoryo, I have tried with the old-style SSL option and it's working. Thanks! But how come the iChat server doesn't allow upgrading to a TLS-encrypted connection via STARTTLS? My colleague installed the latest iOS there ...

Cheers Michael

PS: The log files seems to show some other errors not related to this topic ...

comment:6 Changed 8 years ago by michael.heuberger

By the way it's the Mac OS 10.6 with all its patches on it.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!