powered by Jive Software


this bug openfire? or I stupped?

http://trac.gajim.org/ticket/5665 (my post)

Why do you think this is an Openfire-related issue? I’ve not been able to connect to the domain mentioned in that issue (connection refused), so I have not been able to verify that it is running Openfire.

Openfire hardcodedly adds a host to streamhost elements since 2006, since the inception of the SOCKS5 code in Openfire. It’d be unlikely to go wrong. Can you reproduce this problem using Openfire?

I’m very bad know english, sorry.

This my server, now running, configurations almost default.

Now problem exist.

This is very odd.

Could you please check if this Openfire property exists in your server: xmpp.proxy.externalip

If it does exist, does it have a value?

If it does exist, but has no value: remove the property.

If it does not exist: create it, and use the IP address of your proxy as its value.

Please let me know if any of this worked.


xmpp.proxy.externalip don’t exist, I create this and remove… problem disappeared


So you first created, then removed that property (giving you the same situation that you had) and the problem is gone now?

Yes. Maybe this problem, is not server. Maybe this external factor, i don’t catch this moment