just installed the new latest beta with s2s support.
s2s works pretty well for me, except of the conference rooms. Is this still a missing feature?
Alex
The conference room working in any s2s version(2.2.0beta1) , review your configuration
i mean i want to connect to the conference rooms from another server over s2s. This doesnt work for me.
Alex
i mean i want to connect to the conference rooms from
another server over s2s. This doesnt work for me.
I just tested connecting to conference.jabber.org through my jivesoftware.com connection. Are you getting any error messages about why your test is failing?
Regards,
Matt
Hey Alex,
Is the remote server running JM too? If you are not using JM in the remote server then you may need to register the conference domain (eg. conference.myserver.com) in your DNS so that the remote server would be able to establish a connection to your JM server.
If you are using JM in your remote server then you don’'t need to register the service domain in the DNS server since JM will try to establish a connection to “myserver.com” if “conference.myserver.com” fails.
Regards,
– Gato
Whit neos , gaim and jajc clients work fine , write the url of the server to conect in the browse of your client
i tried to connect to a muc room on the jive server from my other account at myjabber.net. The jive server runs on jabber.ag-software.de, conference is on conference.jabber.ag-software.de. DNS should be OK.
Alex
Hey Alex,
Which server are you using at myjabber.net? Could you turn on the debug log at jabber.ag-software.de and post the debug info that you get when you try to connect from myjabber.net?
Thanks,
– Gato
hi,
here some debug from exodus. I tried to disco the server and conference server. Exodus is trying it several times, but there is never coming a result. But there are existing rooms. Then i tried to join the existing test room and then i always get server connect failed. On myjabber.net a wpjabber server is running.
SENT:
Alex
Alex,
I have 2 comments. 1) Could you try your tests with conference.jivesoftware.com? This will help us narrow down the problem and 2) I will need the debug info that JM is logging in the debug.log file. You can read the debug.log (and enable it) from the admin console.
Thanks,
– Gato
Gato,
i made more tests, also with your public JM on jivesoftware.com. Between my JM and yours everything works perfect. From myjabber.net or jabber.org it doesnt work correct.
I assume the problems are related to the the components and subdomains. Because i can browse jivesoftware.com without problems.
The components
i cant browse and reach at all from other servers than a JM. That is why i cant use groupchat from another server (jabberd1.x) over s2s.
When i browse from my JM other servers then it works too. In the admin console i see one s2s connection for each component and server. Only the other direction has problems. Browse from a jabberd -> JM. It looks like the dialback connection never gets established.
some debug:
2005.07.08 08:12:16 Connect Socket[addr=/205.150.219.4,port=33786,localport=5269]
2005.07.08 08:12:17 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.07.08 08:12:17 RS - Error, incoming connection already exists from: myjabber.net
2005.07.08 08:12:26 Connect Socket[addr=/205.150.219.4,port=33793,localport=5269]
2005.07.08 08:12:27 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.07.08 08:12:27 RS - Error, incoming connection already exists from: myjabber.net
it doesnt accept the connection to the conference.jabber.ag-software.de, i assume it wants to take the connection to jabber.ag-software.de with is always established.
Alex
Hi,
i installed the release version of 2.20. And the problem still exists. I cant browse a JM from another jabberd 1.X or wpjabber server.
Alex
Hey Alex,
Have you turned on the debug log? I would like to see the generated info when jabberd tries to connect to JM.
Thanks,
– Gato
Hi Gato,
here my Debug:
2005.08.05 08:40:18 Connect Socket[addr=/205.150.219.4,port=53538,localport=5269]
2005.08.05 08:40:19 RS - Received dialback key from host: myjabber.net to: jabber.ag-software.de
2005.08.05 08:40:19 RS - Trying to connect to Authoritative Server: myjabber.net:5269
2005.08.05 08:40:19 RS - Connection to AS: myjabber.net:5269 successfull
2005.08.05 08:40:19 RS - Asking AS to verify dialback key for ida25d756a
2005.08.05 08:40:19 RS - Key was VERIFIED by the Authoritative Server for: myjabber.net
2005.08.05 08:40:19 RS - Closing connection to Authoritative Server: myjabber.net
2005.08.05 08:40:19 RS - Sending key verification result to OS: myjabber.net
2005.08.05 08:40:20 OS - Trying to connect to myjabber.net:5269
2005.08.05 08:40:20 OS - Connection to myjabber.net:5269 successfull
2005.08.05 08:40:20 OS - Sent dialback key to host: myjabber.net id: 0cc5503e6a7e0532a1c89f68178eaf45a26c4f7a from domain: jabber.ag-software.de
2005.08.05 08:40:20 AS - Verifying key for host: myjabber.net id: 0cc5503e6a7e0532a1c89f68178eaf45a26c4f7a
2005.08.05 08:40:20 AS - Key was: VALID for host: myjabber.net id: 0cc5503e6a7e0532a1c89f68178eaf45a26c4f7a
2005.08.05 08:40:20 OS - Validation GRANTED from: myjabber.net id: 0cc5503e6a7e0532a1c89f68178eaf45a26c4f7a for domain: jabber.ag-software.de
2005.08.05 08:40:21 Connect Socket[addr=/205.150.219.4,port=53542,localport=5269]
2005.08.05 08:40:22 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.08.05 08:40:22 RS - Error, incoming connection already exists from: myjabber.net
2005.08.05 08:40:31 Connect Socket[addr=/205.150.219.4,port=53551,localport=5269]
2005.08.05 08:40:31 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.08.05 08:40:31 RS - Error, incoming connection already exists from: myjabber.net
2005.08.05 08:40:41 Connect Socket[addr=/205.150.219.4,port=53562,localport=5269]
2005.08.05 08:40:41 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.08.05 08:40:41 RS - Error, incoming connection already exists from: myjabber.net
2005.08.05 08:40:51 Connect Socket[addr=/205.150.219.4,port=53567,localport=5269]
2005.08.05 08:40:52 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.08.05 08:40:52 RS - Error, incoming connection already exists from: myjabber.net
2005.08.05 08:41:21 Connect Socket[addr=/205.150.219.4,port=53595,localport=5269]
2005.08.05 08:41:22 RS - Received dialback key from host: myjabber.net to: conference.jabber.ag-software.de
2005.08.05 08:41:22 RS - Error, incoming connection already exists from: myjabber.net
The server does not accept the other dialback connections for the subdomains (gateways) eg. conference.jabber.ag-software.de[/b].
Alex
I’‘m experiencing a similar problem. I’‘ve been tried to set up a JM server for testing purposes as a possible replacement to the jabberd 1.4 instance that I’‘m currently running. I can generally get presence and do normal chats between the two servers. I can start and use MUC on my old server from an account on the JM server (which I’'m guessing means that s2s at least works in that direction), however, I cannot start or join a MUC on the JM server from my old server.
This always fails. The debug logs look similar to this:
2005.09.15 14:17:11 Connect Socket[addr=/64.151.105.12,port=35692,localport=5269]
2005.09.15 14:17:11 RS - Received dialback key from host: ecotroph.net to: conference.fury.blacka.com
2005.09.15 14:17:11 RS - Error, incoming connection already exists from: ecotroph.net
ya, thats exactly the same problem than mine. It works only in one direction but not vice verca. Which version of JM are you runing?
Alex
ya, thats exactly the same problem than mine. It
works only in one direction but not vice verca. Which
version of JM are you runing?
I’'ve tried both 2.2.1 and 2.3.0-alpha1 and get the same behavior (IIRC). When I posted the above, I was using 2.3.0-a1.
Hello.
I’'ve got the same behaviour with the same error with 2.2.1:
2005.09.18 20:37:16 Connect Socket[addr=/69.55.226.16,port=55687,localport=5269]
2005.09.18 20:37:17 RS - Received dialback key from host: jabber.woof.lu to: search.logicielslibres.info
2005.09.18 20:37:17 RS - Error, incoming connection already exists from: jabber.woof.lu
Here is what I think is going on. Let’'s assume two different jabber servers, A and B. A is some non-JM server (in my case, it is jabberd.1.4), and B is JM. Now B is both B and conference.B.
A makes an s2s connection to B, for presence or whatever. Now B has a session from hostname “A” in the SessionManager.
Next, someone on A tries to create a chat room on “conference.B”. Now server A does not know that “conference.B” and “B” are actually the same server, nor should it. So A creates another[/i] s2s connection to B (really “conference.B”, but they are the same JM instance).
When B gets this connection, what it sees is a duplicate s2s connection from A, and then it rejects that s2s connection.
If I am right, then I would predict that this problem would not arise if no one from B was getting presence from anyone on A (well, in essense, if there was no reason for A to have a pre-existing s2s connection to B) or if ‘‘conference.B’’ was an entirely different JM instance.
I don’‘t know enough about how JM is written to be able to suggest a fix. It could be that JM shouldn’‘t track s2s connections solely by OS hostname, or it could be that JM should track s2s connections to the transports separately, or it could be the JM shouldn’‘t reject “duplicate” s2s sessions. I don’'t know.
Hey guys,
Thanks for the details bug report. I will try to reproduce it and fix it. I will updated this thread when a fix is available.
Thanks,
– Gato