Ejabberd - forbidden c2s session for XMPP Client

I would try first to use a correct domain instead of “localhost”. Somthing like “example.com”.

We have tried that. But it didn’t work

It looks to me as if the error is coming from the bind/2 function in ejabberd_c2s.erl: probably there is a ressource conflict. In other words “Apples-MacBook-Air” is allready bound to an existing connection and the server policy refuses to close this connection and bind the ressource to the new connection.
I could only take a quick look into the configs and could not find a config to change the policy. A quick work around is to use another ressource name.

Thinking more about this, I think no configs should be changed. The issue is on the client side. The client sould try to resume an existing session when reconnecting.

Yes I also thought that issue is from client side but I tried psi + and adium both. But it didn’t work. Also I tried with other resource name like you can see here

iex(7)> :ejabberd_auth.get_users("localhost")   
[
  {"siddhant", "localhost"},
  {"elixirship", "localhost"},
  {"siddhantsingh", "localhost"},
  {"list", "localhost"},
  {"atish", "localhost"},
  {"mishra", "localhost"},
  {"mickael", "localhost"}
]

But it did not change anything.

get_users doesn’t return the resource names. The list shows different users but not the different resources of a single user.

Regarding the configs for setting the policy to drop the old connection I found this:

http://jabber.996255.n3.nabble.com/resource-conflict-td31971.html

The link says, you can set the policy to close the old session by adding this to the configs:
{resource_conflict, closeold}.

{resource_conflict, closeold} is there a key for that? Or just like this, we have to add ?

In the ejabberd.yml file the syntax is:

resource_conflict: closeold

In the example here Session ID mismatch · Issue #2657 · processone/ejabberd · GitHub it is right below

auth_method: internal

Yes I tried this. But I’m getting that error again.

Is trying to reconnect every few second. But it’s failing

iex(3)> [info] (#PID<0.1095.0>) Accepted connection 127.0.0.1:56522 -> 127.0.0.1:5222
[info] (tcp|<0.1095.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1095.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1096.0>) Accepted connection 127.0.0.1:56525 -> 127.0.0.1:5222
[info] (#PID<0.1098.0>) Accepted connection 127.0.0.1:56527 -> 127.0.0.1:5222
[info] (#PID<0.1099.0>) Accepted connection 127.0.0.1:56529 -> 127.0.0.1:5222
[info] (tcp|<0.1099.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1099.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1102.0>) Accepted connection 127.0.0.1:56548 -> 127.0.0.1:5222
[warn] (tcp|<0.1102.0>) Failed c2s DIGEST-MD5 authentication for mickael@localhost from 127.0.0.1: Invalid username or password
[info] (#PID<0.1109.0>) Accepted connection 127.0.0.1:56549 -> 127.0.0.1:5222
[info] (tcp|<0.1109.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1109.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1110.0>) Accepted connection 127.0.0.1:56550 -> 127.0.0.1:5222
[info] (tcp|<0.1110.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1110.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1111.0>) Accepted connection 127.0.0.1:56551 -> 127.0.0.1:5222
[info] (tcp|<0.1111.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1111.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1112.0>) Accepted connection 127.0.0.1:56552 -> 127.0.0.1:5222
[info] (tcp|<0.1112.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1112.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1113.0>) Accepted connection 127.0.0.1:56554 -> 127.0.0.1:5222
[info] (tcp|<0.1113.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1113.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1114.0>) Accepted connection 127.0.0.1:56555 -> 127.0.0.1:5222
[info] (tcp|<0.1114.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1114.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air
[info] (#PID<0.1115.0>) Accepted connection 127.0.0.1:56556 -> 127.0.0.1:5222
[info] (tcp|<0.1115.0>) Accepted c2s DIGEST-MD5 authentication for mickael@localhost by mnesia backend from 127.0.0.1
[warn] (tcp|<0.1115.0>) Forbidden c2s session for mickael@localhost/Apples-MacBook-Air

Any update on this? I’m seeing this issue as well.