Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: essandess
essandess Author
User level: Level 1
41 points

Messages Authentication Stops Working After Server.app 2.2 Upgrade

I just upgraded Server.app to version 2.2. Now Messages authentication has stopped working, I can't use jabber, and the jabber server appears to be broken. Whenever I change my status to Available, I get an error message that says:


Messages can’t log in to username@domainname.com because your login ID or password is incorrect.


This was working before version 2.2, and the exact same network username+password works fine for Mail and other services. I've tried toggling Messages OFF/ON, toggling my Messages service availability OFF/ON, resetting my password, deleting and reinstalling the jabber account, rm ~/Library/Preferences/*iChat*, all to no avail.


Any help would be appreciated. And yes,


sudo serveradmin status jabber

jabber:state = "RUNNING"


The Console error is:


12/11/12 9:06:48.399 PM imagent[594]: [Warning] XMPPConnection: Error: Error Domain=XMPPErrorDomain Code=104 "The operation couldn’t be completed. (XMPPErrorDomain error 104.)" UserInfo=0x9cf012e1d497 {XMPPErrorText=session manager for requested domain is not available}

Mac mini Server (Mid 2010), OS X Mountain Lion (10.8.2), Lion Server, EyeTV HD, Turbo.264 HD

Posted on Dec 11, 2012 6:02 PM

Reply
Question marked as Best reply
User profile for user: essandess
essandess Author
User level: Level 1
41 points

Posted on Dec 11, 2012 6:30 PM

I found the fix, thanks to the Google translation of this Russian post. I want my JIDs to be simple TLDs like domainname.com. But the jabber configuration file /Library/Server/Messages/Config/jabberd/sm.xml specifies FQDNs that look like hostname.domainname.com. If you change this, Messages will work again -- apparently Server.app 2.2 has become more strict about this distinction. Do this:


sudo serveradmin stop jabber

sudo vi /Library/Server/Messages/Config/jabberd/sm.xml

<local>
<!-- Who we identify ourselves as.
Users will have this as the domain part of their JID.
If you want your server to be accessible from other
Jabber servers, this IDs must be FQDN resolvable by DNSes.
If not set, the SM id is used. -->
<id>domainname.com</id>


sudo serveradmin start jabber


Now Messages can authenticate to jabber using simple TLDs like username@domainname.com, just as before.

View in context
3 replies
Question marked as Best reply
User profile for user: essandess
essandess Author
User level: Level 1
41 points

Dec 11, 2012 6:30 PM in response to essandess

I found the fix, thanks to the Google translation of this Russian post. I want my JIDs to be simple TLDs like domainname.com. But the jabber configuration file /Library/Server/Messages/Config/jabberd/sm.xml specifies FQDNs that look like hostname.domainname.com. If you change this, Messages will work again -- apparently Server.app 2.2 has become more strict about this distinction. Do this:


sudo serveradmin stop jabber

sudo vi /Library/Server/Messages/Config/jabberd/sm.xml

<local>
<!-- Who we identify ourselves as.
Users will have this as the domain part of their JID.
If you want your server to be accessible from other
Jabber servers, this IDs must be FQDN resolvable by DNSes.
If not set, the SM id is used. -->
<id>domainname.com</id>


sudo serveradmin start jabber


Now Messages can authenticate to jabber using simple TLDs like username@domainname.com, just as before.

Reply

Messages Authentication Stops Working After Server.app 2.2 Upgrade

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up