Troubleshooting Guide

Most Common Errors

• {urn:ietf:params:xml:ns:xmpp-sasl}mechanism-too-weak - "You are not authorized to perform this action."

  • The authentication mechanisms supported by the client and those reported by the server do not match. Usually, this is because PLAIN is the only mechanism the client and server have in common, but the connection is insecure (example: HTTP instead of HTTPS). Use an HTTPS binding URL (RECOMMENDED), or set the "unsecureAllowed" flag in the connectArgs passed to
    Client.connect() connection arguments (NOT RECOMMENDED).

• {urn:ietf:params:xml:ns:xmpp-streams}service-unavailable - "Could not reach the account server."

  • The BOSH service could not be reached. Verify that the URL listed in the "httpBindingURL" connectArgs is reachable.

• {urn:ietf:params:xml:ns:xmpp-streams}conflict - "This resource is logged in elsewhere."

  • Another client connected with the same username and resourceName as this client. Specify a unique name when creating a jabberwerx.Client instance, or clear the resourceName to have the server generate a unique name for each connection.

• {urn:ietf:params:xml:ns:xmpp-sasl}not-authorized - "Invalid user name or password"

  • As the message specifies, the user name and/or password are not correct; verify the proper values are provided for each.

• {urn:ietf:params:xml:ns:xmpp-stanzas}conflict - "Conflicting names were encountered"

  • Another entity (example: room occupant or pubsub node) already exists with that name. Specify a different name for the entity.

Complete List of Errors

The following table identifies the XMPP stanzas and corresponding error messages that are currently supported by the Error Reporter. In the event that the Error Reporter encounters an XMPP error that is not in the list below, the generic message "Operation failed" will be reported.

XMPP Stanza	Error Reporter Message	Likely Cause
{urn:ietf:params:xml:ns:xmpp-sasl}mechanism-too-weak	You are not authorized to perform this action.	Using PLAIN authentication over an unencrypted connection. Use HTTPS or set the "unsecureAllowed" flag.
{urn:ietf:params:xml:ns:xmpp-sasl}not-authorized	Invalid user name or password.	Either the username or password is incorrect Note: There is only one error condition here, not separate conditions for incorrect username and incorrect pasword).
{urn:ietf:params:xml:ns:xmpp-stanzas}conflict	Conflicting names were encountered.	Another entity (example: room occupant, pubsub node) already exists on that service.
{urn:ietf:params:xml:ns:xmpp-streams}conflict	This resource is logged in elsewhere.	Another client is connected with the same resource (full JID) as this client.
{urn:ietf:params:xml:ns:xmpp-streams}service-unavailable	Could not reach the account server.	The server or recipient does not currently provide the requested service.
{urn:ietf:params:xml:ns:xmpp-sasl}temporary-auth-failure	Unable to login. Check username and password.	The authentication failed because of a temporary error condition on the server.
{urn:ietf:params:xml:ns:xmpp-stanzas}bad-request	The request was not valid.	The request was not formatted correctly according to the relevant protocol.
{urn:ietf:params:xml:ns:xmpp-stanzas}feature-not-implemented	This feature is not yet implemented. Sorry for the inconvenience.	The feature represented in the XML stanza is not implemented by the intended recipient or an intermediate server and therefore the stanza cannot be processed.
{urn:ietf:params:xml:ns:xmpp-stanzas}forbidden	You are not authorized to perform this action.	The requesting entity does not possess the required permissions to perform the action.
{urn:ietf:params:xml:ns:xmpp-stanzas}internal-server-error	An unknown server error occurred. Contact your administrator.	The server has experienced a misconfiguration or an otherwise-undefined internal error that prevents it from servicing the stream.
{urn:ietf:params:xml:ns:xmpp-stanzas}item-not-found.	The requested item could not be found.	The addressed JID or item requested cannot be found.
{urn:ietf:params:xml:ns:xmpp-stanzas}jid-malformed.	The JID is not valid.	The sending entity has provided or communicated an XMPP address (example: a value of the 'to' attribute) or aspect thereof (example: a resource identifier) that does not adhere to the syntax defined in RFC6122.
{urn:ietf:params:xml:ns:xmpp-stanzas}not-acceptable.	The given information was not acceptable.	The stanza size does not meet the server's configured limits. Please look for the application-specific error condition (<max/>, <min/>.etc).
{urn:ietf:params:xml:ns:xmpp-stanzas}not-allowed.	You are not allowed to perform this action.	The recipient or server does not allow any entity to perform the action.
{urn:ietf:params:xml:ns:xmpp-stanzas}not-authorized.	You are not authorized to perform this action.	The sender must provide proper credentials before being allowed to perform the action, or has provided improper credentials.
{urn:ietf:params:xml:ns:xmpp-stanzas}registration-required.	You must register with the service before continuing.	The requesting entity is not authorized to access the requested service because registration is required. Please register with the service.
{urn:ietf:params:xml:ns:xmpp-stanzas}remote-server-not-found.	Could not find the requested server.	A remote server or service specified as part or all of the JID of the intended recipient does not exist.
{urn:ietf:params:xml:ns:xmpp-stanzas}remote-server-timeout.	Unable to contact the server.	A remote server or service specified as part or all of the JID of the intended recipient (or required to fulfill a request) could not be contacted within a reasonable amount of time.
{urn:ietf:params:xml:ns:xmpp-stanzas}service-unavailable.	This service is not available. Try again later.	BOSH URL is not accessible from the browser. Verify that the BOSH service is running, and CORS is supported or the proxy is running correctly.
{urn:ietf:params:xml:ns:xmpp-stanzas}undefined-condition.	An unknown error occurred. Contact your administrator.	The error condition is not one of those defined by the other conditions. Please look for the application-specific error condition.
{urn:ietf:params:xml:ns:xmpp-stanzas}unexpected-request.	Did not expect the request at this time.	The recipient or server understood the request but was not expecting it at this time (for example, the request was out of order).

Community

Visit the Jabber Developer Forums to ask questions and interact with other developers. Forums.