[jitsi-users] Cannot connect across servers


#1

I'm not sure if this is a temprary problem, but I've created an
account on the @jit.si domain, however I've come across two issues:

1) Users on other xmpp servers cannot either contact me on @jit.si,
nor can they use XMPP service discovery on jit.si (404 and sometimes
503),
2) I cannot contact those on other domains and service discovery
requests seem to time out before eventually ending in 404's in the
XMPP console.

If I understand correctly XMPP should work across servers and domains,
and indeed on other accounts I can. Is jit.si not a reliable server to
use?


#2

Finaly somebody else complaining, yay.
I have the same problem, but (as stated earlier) only for some
servers, not for all.

- --
Yannik V�lker

···

Am 12.07.2013 19:23, schrieb feywolf@hushmail.com:

I'm not sure if this is a temprary problem, but I've created an
account on the @jit.si domain, however I've come across two
issues:

1) Users on other xmpp servers cannot either contact me on @jit.si,
nor can they use XMPP service discovery on jit.si (404 and
sometimes 503), 2) I cannot contact those on other domains and
service discovery requests seem to time out before eventually
ending in 404's in the XMPP console.

If I understand correctly XMPP should work across servers and
domains, and indeed on other accounts I can. Is jit.si not a
reliable server to use?


#3

Answer is still the same: Tell us what you believe jit.si is doing wrong
and we'll try to fix it or we'll relay to the openfire forum.

--sent from my mobile

···

On Jul 12, 2013 7:39 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 12.07.2013 19:23, schrieb feywolf@hushmail.com:
> I'm not sure if this is a temprary problem, but I've created an
> account on the @jit.si domain, however I've come across two
> issues:
>
> 1) Users on other xmpp servers cannot either contact me on @jit.si,
> nor can they use XMPP service discovery on jit.si (404 and
> sometimes 503), 2) I cannot contact those on other domains and
> service discovery requests seem to time out before eventually
> ending in 404's in the XMPP console.
>
> If I understand correctly XMPP should work across servers and
> domains, and indeed on other accounts I can. Is jit.si not a
> reliable server to use?

Finaly somebody else complaining, yay.
I have the same problem, but (as stated earlier) only for some
servers, not for all.

- --
Yannik Völker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJR4D85AAoJEDqk81AiCyXKoIMP/jnbJ9evlyrWsN/hUrGTe+Nu
v5WcdYBBsd6dRgHbIHCD09dM8ckJ18eLUCROkXBRZwQMxrWw/Ke4jOQ2lMicbZKH
vicCVdhRvnzLdtSCFTL7fEFmykkUhPvLC7ISr+JynDG8GN6eWpIWgNfcvCARXDmI
GVjewkRbI8WYWjWkj2C8+E05inUXiM1Ua5TAyBgJiwZBic1DNE17bBNFrBzv8DpK
NOcZN2jM0AQUmToneWiT1fJKQJPeULmnAdp10y3t9z/aJbu5Q50XDCZr3mGme/ZA
DIyd/B6M5ne8FpQqch0CZoRzOvRsk9MOkb2N2LwYqd4Dc2zyeRTiaZmrZhj6yHCX
vp1ifSDLO+/V4J2MRKZT0Jx2LAxhcqKqWzabny+rhC846ryuybxD1WUe3JfmQF6P
2sjBpEAOEr3slyLmd/PkdgnkNGCGkYHZV6Axa1/wI91gqvWgGgANt0wqpPZ7e6Mo
aEjwYys38UCDKQDeCxIx5hxQuxK1Yl3lCbu4YUOzFy+JqXxVk4Ws6E1MXj8maY0B
UnE33WLXSb7hZF1pZ5x1M2ILKdVen0kSCoKqj2wdS2wwbGMqxIOIASpAhFQmpWyk
I8aIYZ9/8dtoEYA+wDrGTJ4ykRb/X5ik+RB51DJyafBPogwPolurg3QXvNl0MZHJ
WHtHtQLIoAL1AUSNAEz2
=Ks8S
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

I'm afraid I don't know enough about XMPP to know exactly what is going wrong, all I know is that something is keeping the cross-connection (is it called "federation"?) from working properly.

Briefly, the message "communication with remote domains is not enabled" flashed across the XMPP console while I was trying to figure out if it was a local error. I've only seen it once, and I've been unable to replicate that specific message, the rest is 404's.

Here's a snippet from Pidgin's XMPP from when you try to do a service discovery from @comm.unicate.me to jit.si

<iq type=‘get’ to=‘jit.si’ id=‘purpledisco2c6d1511’>
  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>
<iq from=‘jit.si’ to=’***@comm.unicate.me/desktop’ type=‘error’ id=‘purpledisco2c6d1511’>
  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
  <error code=‘404’ type=‘cancel’>
    <remote-server-not-found xmlns=‘urn:ietf:params:xml:ns:xmpp-stanzas’/>
  </error>
</iq>

I have tried variations of jit.si, such as xmpp.jit.si (which I found after a dig to see if it was a local DNS issue), as well as jitsi.org and the rDNS record of "5.135.86.61" for xmpp.jit.si.

Trying to do a service request TO comm.unicate.me from my jit.si account results in a lengthy delay, followed by this in the XMPP console:
<iq type=‘get’ to=‘comm.unicate.me’ id=‘purpledisco97af8b1a’>
    <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>

//insert 4 minute delay here

<iq type=‘result’ id=‘purpleb836fdfe’ to=***@jit.si/pidgin’/>
<iq type=‘error’ id=‘purpledisco97af8b1a’ to=’***@jit.si/pidgin’ from=‘comm.unicate.me’>
    <query xmlns=‘http://jabber.org/protocol/disco#info’/>
    <error code=‘404’ type=‘cancel’>
        <remote-server-not-found xmlns=‘urn:ietf:params:xml:ns:xmpp-stanzas’/>
    </error>
</iq>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

···

On 07/12/2013 at 8:53 PM, "Emil Ivov" <emcho@jitsi.org> wrote:Answer is still the same: Tell us what you believe jit.si is doing wrong and we'll try to fix it or we'll relay to the openfire forum.--sent from my mobileOn Jul 12, 2013 7:39 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:

Am 12.07.2013 19:23, schrieb feywolf@hushmail.com:

I'm not sure if this is a temprary problem, but I've created an
account on the @jit.si domain, however I've come across two
issues:

1) Users on other xmpp servers cannot either contact me on @jit.si,
nor can they use XMPP service discovery on jit.si (404 and
sometimes 503), 2) I cannot contact those on other domains and
service discovery requests seem to time out before eventually
ending in 404's in the XMPP console.

If I understand correctly XMPP should work across servers and
domains, and indeed on other accounts I can. Is jit.si not a
reliable server to use?

Finaly somebody else complaining, yay.
I have the same problem, but (as stated earlier) only for some
servers, not for all.

- --
Yannik Völker

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

hmm? maybee try removing swing.bluejimp.com from the dns records
entirely (not just assigning it a lower priority).
other then that: i do not have the logfiles you might have so i am in
the worse situation for debugging this issue.

- --
Yannik V�lker

···

Am 12.07.2013 20:50, schrieb Emil Ivov:

Answer is still the same: Tell us what you believe jit.si
<http://jit.si> is doing wrong and we'll try to fix it or we'll
relay to the openfire forum.


#6

Hey there,

I'm afraid I don't know enough about XMPP to know exactly what is going wrong, all I know is that something is keeping the cross-connection (is it called "federation"?) from working properly.

Well. I regularly chat with users from jabber.org, gmail.com (and other google apps domains) and a number of other private servers. I am not saying there is absolutely no problem but it doesn't appear always.

More below.

Briefly, the message "communication with remote domains is not enabled" flashed across the XMPP console while I was trying to figure out if it was a local error. I've only seen it once, and I've been unable to replicate that specific message, the rest is 404's.

Here's a snippet from Pidgin's XMPP from when you try to do a service discovery from @comm.unicate.me to jit.si

<iq type=‘get’ to=‘jit.si’ id=‘purpledisco2c6d1511’>
  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>
<iq from=‘jit.si’ to=’***@comm.unicate.me/desktop’ type=‘error’ id=‘purpledisco2c6d1511’>
  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
  <error code=‘404’ type=‘cancel’>
    <remote-server-not-found xmlns=‘urn:ietf:params:xml:ns:xmpp-stanzas’/>
  </error>
</iq>

I have tried variations of jit.si, such as xmpp.jit.si (which I found after a dig to see if it was a local DNS issue), as well as jitsi.org and the rDNS record of "5.135.86.61" for xmpp.jit.si.

Trying to do a service request TO comm.unicate.me from my jit.si account results in a lengthy delay, followed by this in the XMPP console:
<iq type=‘get’ to=‘comm.unicate.me’ id=‘purpledisco97af8b1a’>
     <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>

//insert 4 minute delay here

<iq type=‘result’ id=‘purpleb836fdfe’ to=***@jit.si/pidgin’/>
<iq type=‘error’ id=‘purpledisco97af8b1a’ to=’***@jit.si/pidgin’ from=‘comm.unicate.me’>
     <query xmlns=‘http://jabber.org/protocol/disco#info’/>
     <error code=‘404’ type=‘cancel’>
         <remote-server-not-found xmlns=‘urn:ietf:params:xml:ns:xmpp-stanzas’/>
     </error>
</iq>

Servers would generally not return disco info for people that are not on the roster of the requestor. Similarly I believe many would allow querying their own disco info, only to entities that they have directly authenticated (or that are somehow white listed). That's what XEP-0030 seems to advise.

Emil

···

On 12.07.13, 21:17, feywolf@hushmail.com wrote:

On 07/12/2013 at 8:53 PM, "Emil Ivov" <emcho@jitsi.org> wrote:Answer is still the same: Tell us what you believe jit.si is doing wrong and we'll try to fix it or we'll relay to the openfire forum.--sent from my mobileOn Jul 12, 2013 7:39 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 12.07.2013 19:23, schrieb feywolf@hushmail.com:

I'm not sure if this is a temprary problem, but I've created an
account on the @jit.si domain, however I've come across two
issues:

1) Users on other xmpp servers cannot either contact me on @jit.si,
nor can they use XMPP service discovery on jit.si (404 and
sometimes 503), 2) I cannot contact those on other domains and
service discovery requests seem to time out before eventually
ending in 404's in the XMPP console.

If I understand correctly XMPP should work across servers and
domains, and indeed on other accounts I can. Is jit.si not a
reliable server to use?

Finaly somebody else complaining, yay.
I have the same problem, but (as stated earlier) only for some
servers, not for all.

- --
Yannik Völker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJR4D85AAoJEDqk81AiCyXKoIMP/jnbJ9evlyrWsN/hUrGTe+Nu
v5WcdYBBsd6dRgHbIHCD09dM8ckJ18eLUCROkXBRZwQMxrWw/Ke4jOQ2lMicbZKH
vicCVdhRvnzLdtSCFTL7fEFmykkUhPvLC7ISr+JynDG8GN6eWpIWgNfcvCARXDmI
GVjewkRbI8WYWjWkj2C8+E05inUXiM1Ua5TAyBgJiwZBic1DNE17bBNFrBzv8DpK
NOcZN2jM0AQUmToneWiT1fJKQJPeULmnAdp10y3t9z/aJbu5Q50XDCZr3mGme/ZA
DIyd/B6M5ne8FpQqch0CZoRzOvRsk9MOkb2N2LwYqd4Dc2zyeRTiaZmrZhj6yHCX
vp1ifSDLO+/V4J2MRKZT0Jx2LAxhcqKqWzabny+rhC846ryuybxD1WUe3JfmQF6P
2sjBpEAOEr3slyLmd/PkdgnkNGCGkYHZV6Axa1/wI91gqvWgGgANt0wqpPZ7e6Mo
aEjwYys38UCDKQDeCxIx5hxQuxK1Yl3lCbu4YUOzFy+JqXxVk4Ws6E1MXj8maY0B
UnE33WLXSb7hZF1pZ5x1M2ILKdVen0kSCoKqj2wdS2wwbGMqxIOIASpAhFQmpWyk
I8aIYZ9/8dtoEYA+wDrGTJ4ykRb/X5ik+RB51DJyafBPogwPolurg3QXvNl0MZHJ
WHtHtQLIoAL1AUSNAEz2
=Ks8S
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.org


#7

I have to second this.
I really don't know how you expect end-users to figure out what's going wrong when we don't have the logs you guys do, nor can we see what the server configuration is.

I've given what little information I've been able to gather from my XMPP client(s), and I admit my earlier theories were completely wrong.
I have contacted the administrator of comm.unicate.me, as someone suggested in another thread, but have yet to get any real reply other than a "I'll look at it later". I'm not sure why end-users are being asked to act as liaison between server maintainers.

···

On 07/15/2013 at 2:31 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:

Am 12.07.2013 20:50, schrieb Emil Ivov:

Answer is still the same: Tell us what you believe jit.si
<http://jit.si> is doing wrong and we'll try to fix it or we'll
relay to the openfire forum.

hmm? maybee try removing swing.bluejimp.com from the dns records
entirely (not just assigning it a lower priority).
other then that: i do not have the logfiles you might have so i am
in
the worse situation for debugging this issue.

--
Yannik Völker


#8

Aha. Well, that's understandable, actually.

Still, the problem remains in that with all servers (except one, see below) I've now created an account on to test (comm.unicate.me and jabber.se), none of them seem to be able to talk to jit.si. I was going to try jabber.org just now, but they seem to have disabled registration of new accounts due due a database move.

The error for contact authorization/adding a contact is similar to the previous errors.
In Jitsi (on jit.si account), trying to add a contact on @jabber.se results in a constant "Waiting for authorization". Trying to send a message results in error "The above message could not be delivered Failed to deliver message." What's interesting is that the other side, namely the @jabber.se account, never receives the authorization request which I've seen come up on other jabber accounts, (such as adding my test jabber.se to my test comm.unicate.me account), namely the Accent or Deny thing.

In Pidgin, the process is the same, but in that under the @jit.si buddy, there's an additional "Error: 404: Remote server not found"

Interestingly, I've made a 3rd account now to test things out, this time on jabber.rootbash.com, which also uses OpenFire (the others do not), and the results are exactly the same. I'm starting to wonder if this has more to do with OpenFire itself than with something with jit.si itself.
However! Trying to add my jit.si account as a buddy on the jabber.rootbash.com actually works! There's no problem between the two, making me again wonder if this has something to do with OpenFire. I'm not sure what that would be, though.

After checking the OpenFire forums, there are some threads about cross-server communication.
But then again, it seems to work for you (and many others, or I imagine there would be more complaints/bug reports)... Hmm.

As I've said, I'm no expert on XMPP, and I'm really not sure what's wrong. However, these are my observations on what's happening.

···

On 07/13/2013 at 1:55 AM, "Emil Ivov" <emcho@jitsi.org> wrote:

Hey there,

On 12.07.13, 21:17, feywolf@hushmail.com wrote:

I'm afraid I don't know enough about XMPP to know exactly what

is going wrong, all I know is that something is keeping the cross-
connection (is it called "federation"?) from working properly.

Well. I regularly chat with users from jabber.org, gmail.com (and
other
google apps domains) and a number of other private servers. I am
not
saying there is absolutely no problem but it doesn't appear always.

More below.

Briefly, the message "communication with remote domains is not

enabled" flashed across the XMPP console while I was trying to
figure out if it was a local error. I've only seen it once, and
I've been unable to replicate that specific message, the rest is
404's.

Here's a snippet from Pidgin's XMPP from when you try to do a

service discovery from @comm.unicate.me to jit.si

<iq type=‘get’ to=‘jit.si’ id=‘purpledisco2c6d1511’>
  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>
<iq from=‘jit.si’ to=’***@comm.unicate.me/desktop’ type=‘error’

id='purpledisco2c6d1511'>

  <query xmlns=‘http://jabber.org/protocol/disco#info’/>
  <error code=‘404’ type=‘cancel’>
    <remote-server-not-found xmlns='urn:ietf:params:xml:ns:xmpp-

stanzas'/>

  </error>
</iq>

I have tried variations of jit.si, such as xmpp.jit.si (which I

found after a dig to see if it was a local DNS issue), as well as
jitsi.org and the rDNS record of "5.135.86.61" for xmpp.jit.si.

Trying to do a service request TO comm.unicate.me from my jit.si

account results in a lengthy delay, followed by this in the XMPP
console:

<iq type=‘get’ to=‘comm.unicate.me’ id=‘purpledisco97af8b1a’>
     <query xmlns=‘http://jabber.org/protocol/disco#info’/>
</iq>

//insert 4 minute delay here

<iq type='result' id='purpleb836fdfe' to=***@jit.si/pidgin'/>
<iq type='error' id='purpledisco97af8b1a' to='***@jit.si/pidgin'

from='comm.unicate.me'>

     <query xmlns=‘http://jabber.org/protocol/disco#info’/>
     <error code=‘404’ type=‘cancel’>
         <remote-server-not-found

xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>

     </error>
</iq>

Servers would generally not return disco info for people that are
not on
the roster of the requestor. Similarly I believe many would allow
querying their own disco info, only to entities that they have
directly
authenticated (or that are somehow white listed). That's what XEP-
0030
seems to advise.

Emil

On 07/12/2013 at 8:53 PM, "Emil Ivov" <emcho@jitsi.org>

wrote:Answer is still the same: Tell us what you believe jit.si is
doing wrong and we'll try to fix it or we'll relay to the openfire
forum.--sent from my mobileOn Jul 12, 2013 7:39 PM, "Yannik
Völker" <yannikv@yahoo.de> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 12.07.2013 19:23, schrieb feywolf@hushmail.com:

I'm not sure if this is a temprary problem, but I've created an
account on the @jit.si domain, however I've come across two
issues:

1) Users on other xmpp servers cannot either contact me on

@jit.si,

nor can they use XMPP service discovery on jit.si (404 and
sometimes 503), 2) I cannot contact those on other domains and
service discovery requests seem to time out before eventually
ending in 404's in the XMPP console.

If I understand correctly XMPP should work across servers and
domains, and indeed on other accounts I can. Is jit.si not a
reliable server to use?

Finaly somebody else complaining, yay.
I have the same problem, but (as stated earlier) only for some
servers, not for all.

- --
Yannik Völker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJR4D85AAoJEDqk81AiCyXKoIMP/jnbJ9evlyrWsN/hUrGTe+Nu
v5WcdYBBsd6dRgHbIHCD09dM8ckJ18eLUCROkXBRZwQMxrWw/Ke4jOQ2lMicbZKH
vicCVdhRvnzLdtSCFTL7fEFmykkUhPvLC7ISr+JynDG8GN6eWpIWgNfcvCARXDmI
GVjewkRbI8WYWjWkj2C8+E05inUXiM1Ua5TAyBgJiwZBic1DNE17bBNFrBzv8DpK
NOcZN2jM0AQUmToneWiT1fJKQJPeULmnAdp10y3t9z/aJbu5Q50XDCZr3mGme/ZA
DIyd/B6M5ne8FpQqch0CZoRzOvRsk9MOkb2N2LwYqd4Dc2zyeRTiaZmrZhj6yHCX
vp1ifSDLO+/V4J2MRKZT0Jx2LAxhcqKqWzabny+rhC846ryuybxD1WUe3JfmQF6P
2sjBpEAOEr3slyLmd/PkdgnkNGCGkYHZV6Axa1/wI91gqvWgGgANt0wqpPZ7e6Mo
aEjwYys38UCDKQDeCxIx5hxQuxK1Yl3lCbu4YUOzFy+JqXxVk4Ws6E1MXj8maY0B
UnE33WLXSb7hZF1pZ5x1M2ILKdVen0kSCoKqj2wdS2wwbGMqxIOIASpAhFQmpWyk
I8aIYZ9/8dtoEYA+wDrGTJ4ykRb/X5ik+RB51DJyafBPogwPolurg3QXvNl0MZHJ
WHtHtQLIoAL1AUSNAEz2
=Ks8S
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.org


#9

Hey there,

I have to second this. I really don't know how you expect end-users
to figure out what's going wrong when we don't have the logs you guys
do, nor can we see what the server configuration is.

I don't believe anyone has set such an expectation. We have however indicated that if people are willing to help with the issue, that's one way to do it.

I've given what little information I've been able to gather from my
XMPP client(s), and I admit my earlier theories were completely
wrong. I have contacted the administrator of comm.unicate.me, as
someone suggested in another thread, but have yet to get any real
reply other than a "I'll look at it later". I'm not sure why
end-users are being asked to act as liaison between server
maintainers.

There's nothing, wrong with asking for help, is there? You seem to be comfortable doing it :wink:

Seriously guys. We are not service maintainers. Currently jit.si is out there to provide a service that works well with Jitsi and that allows for testing video calls. This may change in the future and we (BlueJimp) may start running it in a different way but we are not there yet. We'll let you know when this happens!

So until then, if it's good enough for you, awesome! If not, then I suggest you try running your own service, or you use another one.

Cheers,
Emil

···

On 18.07.13, 21:36, feywolf@hushmail.com wrote:

On 07/15/2013 at 2:31 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:

Am 12.07.2013 20:50, schrieb Emil Ivov:

Answer is still the same: Tell us what you believe jit.si
<http://jit.si> is doing wrong and we'll try to fix it or we'll
relay to the openfire forum.

hmm? maybee try removing swing.bluejimp.com from the dns records
entirely (not just assigning it a lower priority). other then that:
i do not have the logfiles you might have so i am in the worse
situation for debugging this issue.

-- Yannik Völker

_______________________________________________ users mailing list
users@jitsi.org Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.org


#10

While i think that this is realy not my job i have investigated a bit
further:
as far as i could investigate the connection problems only happen
between ejabberd servers and jit.si.
attention, capslock incoming:

OTHER OPENFIRE SERVERS COMMUNICATE WITH THOSE JUST FINE SO IT IS
_YOUR_ FAULT

i think that you are not putting enought time and energy into solving
this fundamental problem. There is something wrong with your
configuration and you have not fixed it since i first reported it
about 2 months ago. this is not good and i am realy not happy anymore.
just go throught the logs and or the settings and try untill it is
fixed, that can not be too hard, can it?

···

Am 18.07.2013 21:36, schrieb feywolf@hushmail.com:

I have to second this. I really don't know how you expect
end-users to figure out what's going wrong when we don't have the
logs you guys do, nor can we see what the server configuration is.

I've given what little information I've been able to gather from
my XMPP client(s), and I admit my earlier theories were completely
wrong. I have contacted the administrator of comm.unicate.me, as
someone suggested in another thread, but have yet to get any real
reply other than a "I'll look at it later". I'm not sure why
end-users are being asked to act as liaison between server
maintainers.

On 07/15/2013 at 2:31 PM, "Yannik Völker" <yannikv@yahoo.de> > wrote:

Am 12.07.2013 20:50, schrieb Emil Ivov:

Answer is still the same: Tell us what you believe jit.si
<http://jit.si> is doing wrong and we'll try to fix it or we'll
relay to the openfire forum.

hmm? maybee try removing swing.bluejimp.com from the dns records
entirely (not just assigning it a lower priority). other then
that: i do not have the logfiles you might have so i am in the
worse situation for debugging this issue.

-- Yannik Völker

_______________________________________________ users mailing list
users@jitsi.org Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

not cool
- -- Yannik Völker


#11

I do not belive that it is a problem with openfire as
jit.si<-->jabber-server.de works and jabber-server.de uses openfire,
additionally i know that one connection to an ejabberd2 does not.

- --
Yannik Völker

···

Am 13.07.2013 09:45, schrieb feywolf@hushmail.com:

Aha. Well, that's understandable, actually.

Still, the problem remains in that with all servers (except one,
see below) I've now created an account on to test (comm.unicate.me
and jabber.se), none of them seem to be able to talk to jit.si. I
was going to try jabber.org just now, but they seem to have
disabled registration of new accounts due due a database move.

The error for contact authorization/adding a contact is similar to
the previous errors. In Jitsi (on jit.si account), trying to add a
contact on @jabber.se results in a constant "Waiting for
authorization". Trying to send a message results in error "The
above message could not be delivered Failed to deliver message."
What's interesting is that the other side, namely the @jabber.se
account, never receives the authorization request which I've seen
come up on other jabber accounts, (such as adding my test jabber.se
to my test comm.unicate.me account), namely the Accent or Deny
thing.

In Pidgin, the process is the same, but in that under the @jit.si
buddy, there's an additional "Error: 404: Remote server not found"

Interestingly, I've made a 3rd account now to test things out, this
time on jabber.rootbash.com, which also uses OpenFire (the others
do not), and the results are exactly the same. I'm starting to
wonder if this has more to do with OpenFire itself than with
something with jit.si itself. However! Trying to add my jit.si
account as a buddy on the jabber.rootbash.com actually works!
There's no problem between the two, making me again wonder if this
has something to do with OpenFire. I'm not sure what that would be,
though.

After checking the OpenFire forums, there are some threads about
cross-server communication. But then again, it seems to work for
you (and many others, or I imagine there would be more
complaints/bug reports)... Hmm.

As I've said, I'm no expert on XMPP, and I'm really not sure what's
wrong. However, these are my observations on what's happening.


#12

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While i think that this is realy not my job i have investigated a bit
further:
as far as i could investigate the connection problems only happen
between ejabberd servers and jit.si.

Nope. That's wrong. I've just tried with an ejabberd installation and it worked.

attention, capslock incoming:

Aha! That's a good way to get help!

OTHER OPENFIRE SERVERS COMMUNICATE WITH THOSE JUST FINE SO IT IS
_YOUR_ FAULT

Entirely possible.

i think that you are not putting enought time and energy into solving
this fundamental problem. There is something wrong with your
configuration and you have not fixed it since i first reported it
about 2 months ago. this is not good and i am realy not happy anymore.

Help me understand here. Didn't you mention that you had other servers out there that provide a reliable XMPP service and Jingle Node relays? If so why do you peek using jit.si in spite of your problems? Is it because you just enjoy yelling at us too much? :slight_smile:

just go throught the logs and or the settings and try untill it is
fixed, that can not be too hard, can it?

We've already went through the logs but for some reason, that alone doesn't seem to fix the problem ...

That said I personally find this attitude quite unacceptable. Therefore, Yannik, please do not use this server anymore.

To everyone else: we are aware that the problem exists. We've looked into it already and we'll do so again when we can. Until then (and there's no telling when "then" will be), if you can't federate with the servers that you need to, then please feel free to use another XMPP service.

Emil

···

On 18.07.13, 22:34, Yannik Völker wrote:

Am 18.07.2013 21:36, schrieb feywolf@hushmail.com:

I have to second this. I really don't know how you expect
end-users to figure out what's going wrong when we don't have the
logs you guys do, nor can we see what the server configuration is.

I've given what little information I've been able to gather from
my XMPP client(s), and I admit my earlier theories were completely
wrong. I have contacted the administrator of comm.unicate.me, as
someone suggested in another thread, but have yet to get any real
reply other than a "I'll look at it later". I'm not sure why
end-users are being asked to act as liaison between server
maintainers.

On 07/15/2013 at 2:31 PM, "Yannik Völker" <yannikv@yahoo.de> >> wrote:

Am 12.07.2013 20:50, schrieb Emil Ivov:

Answer is still the same: Tell us what you believe jit.si
<http://jit.si> is doing wrong and we'll try to fix it or we'll
relay to the openfire forum.

hmm? maybee try removing swing.bluejimp.com from the dns records
entirely (not just assigning it a lower priority). other then
that: i do not have the logfiles you might have so i am in the
worse situation for debugging this issue.

-- Yannik Völker

_______________________________________________ users mailing list
users@jitsi.org Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

not cool
- -- Yannik Völker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJR6FFKAAoJEDqk81AiCyXKGqcP+wf5cRNHH/nTgis8a0bh7/9/
M8/Lv8PS43OyFanL3HBEhWuW4zBlhUQEjYJT9hsn37wkJCGIY15f4O0JacBinBDQ
B9UnUyc5rQj8Elm0o4lIjuiwxR0Hpq189mxVSO8YCExYTaYKArJ9q0a3y+a5w7D5
4e7uKz4UoaMreSjK39hdpqps1UQ+lhgybz4mUlcVXIsZRy4TN5P224FH9KG6GU1r
U4Y+wa1Hak0rCSEveg5W2t3tD0KF6w82ZGwY/X+k9UU7KRpJH6WGgPqZg2PaFJyK
2n36+4EI3iBpE0FcIF8xBtEqFEY7xOlKmPTBkZtDgVSBv4YoXEQ+qfvp9i0tKPkf
KXI2HoBA5gn3uT3akSCPlNlcupOUwPmfxQCD788UfrcQB2ZmoQsm+VRT3/2oRBt5
NZ969IY9vjfxCMcCtwOHKdVIiBnJ/we2ln2yVjRk6r9HoieAPxFKXubXuqF/q38c
q06t4QD1duSGA7vQQGlgJ+XkMQ+e0BL857X38UvOECoxyJ0+Ryyr0Zuheu1N7aDU
kZ2C34dQGStU11Pg2u5OVKtdOxrNEADtCrnwwyDQLGn+euZNI/J6fLkj7PQ0OuUw
A7YQyvdk1fkK9pbKQjUTMZ2WF3LOvRh6sstiAGZcu70u3jLmPRYPfOQH76FndR7x
Rwt+ndCMscu42W6L6BBV
=zVC1
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.org


#13

Yeah, I've realized it's not OpenFire in the past few hours of fiddling with things.
I set up a local OpenFire XMPP server to see if it was, and of course, it's not OF.

Which really just adds to my confusion. I really can't tell if this is a local problem on my end, something server side, or a combination of the two. The only way I've been able to replicate this problem on my own server is by disabling Server to Server in the OF control panel, and I doubt the jit.si webdudes have that set to disabled or filtered with a whitelist. (My test server can communicate with jit.si just fine.)

At this point, I'm stumped. Some domains can connect to jit.si, some can not.

For reference, and if it helps, here is a summary of the domains I've tested, and whether or not my accounts on them can connect to jit.si:

@jabber.se - No (from my end)
@comm.unicate.me - No (from my end)
@jabber.rootbash.com - Yes (from my end)

Is there anything you jit.si webdudes want me to run and log to help?

···

On 07/13/2013 at 1:55 PM, "Yannik Völker" <yannikv@yahoo.de> wrote:

Am 13.07.2013 09:45, schrieb feywolf@hushmail.com:

Aha. Well, that's understandable, actually.

Still, the problem remains in that with all servers (except one,
see below) I've now created an account on to test

(comm.unicate.me

and jabber.se), none of them seem to be able to talk to jit.si. I
was going to try jabber.org just now, but they seem to have
disabled registration of new accounts due due a database move.

The error for contact authorization/adding a contact is similar

to

the previous errors. In Jitsi (on jit.si account), trying to add

a

contact on @jabber.se results in a constant "Waiting for
authorization". Trying to send a message results in error "The
above message could not be delivered Failed to deliver message."
What's interesting is that the other side, namely the @jabber.se
account, never receives the authorization request which I've seen
come up on other jabber accounts, (such as adding my test

jabber.se

to my test comm.unicate.me account), namely the Accent or Deny
thing.

In Pidgin, the process is the same, but in that under the @jit.si
buddy, there's an additional "Error: 404: Remote server not

found"

Interestingly, I've made a 3rd account now to test things out,

this

time on jabber.rootbash.com, which also uses OpenFire (the others
do not), and the results are exactly the same. I'm starting to
wonder if this has more to do with OpenFire itself than with
something with jit.si itself. However! Trying to add my jit.si
account as a buddy on the jabber.rootbash.com actually works!
There's no problem between the two, making me again wonder if

this

has something to do with OpenFire. I'm not sure what that would

be,

though.

After checking the OpenFire forums, there are some threads about
cross-server communication. But then again, it seems to work for
you (and many others, or I imagine there would be more
complaints/bug reports)... Hmm.

As I've said, I'm no expert on XMPP, and I'm really not sure

what's

wrong. However, these are my observations on what's happening.

I do not belive that it is a problem with openfire as
jit.si<-->jabber-server.de works and jabber-server.de uses
openfire,
additionally i know that one connection to an ejabberd2 does not.

--
Yannik Völker


#14

Yeah, I've realized it's not OpenFire in the past few hours of
fiddling with things. I set up a local OpenFire XMPP server to see
if it was, and of course, it's not OF.

Which really just adds to my confusion. I really can't tell if this
is a local problem on my end, something server side, or a
combination of the two. The only way I've been able to replicate
this problem on my own server is by disabling Server to Server in
the OF control panel, and I doubt the jit.si webdudes have that set
to disabled or filtered with a whitelist. (My test server can
communicate with jit.si just fine.)

This is not a problem on your end, its a problem of the communication
between jutsi and the servers.

For reference, and if it helps, here is a summary of the domains
I've tested, and whether or not my accounts on them can connect to
jit.si:

@jabber.se - No (from my end) @comm.unicate.me - No (from my end)
@jabber.rootbash.com - Yes (from my end)

@draugr.de - No

- --
Yannik Völker

···

Am 13.07.2013 14:43, schrieb feywolf@hushmail.com: