Port confusions

9 views
Skip to first unread message

.M.

unread,
Aug 14, 2009, 11:34:17 AM8/14/09
to Sydney Google Wave User Group
Hi all

I'm having difficulty getting federation to work and wondering if my
confusion over ports is the problem

This is the style of error I get when I try to add remote users

<iq type="error" id="4101-1" to="wave.rackandpin.com"
from="wave.collaborynth.com.au">
<query xmlns="http://jabber.org/protocol/disco#items"/>
<error code="404" type="cancel">
<remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-
stanzas"/>
</error>
</iq>

Can I check the logic here with you all?

Port WFS uses to communicate with local XMPP sever = 5275

Port specified in run-server.sh - xmpp_server_port=5275

Port XMPP servers use to communicate with each other = 5269

Q) So why does Openfire Server Manager | System Properties |
xmpp.component.socket.port change from 5269 to 5275 if you set Server
Settings | External Components Settings | Service Enabled | Enabled |
Port 5275

Thanks
.M.

Harrison Conlin

unread,
Aug 17, 2009, 4:05:00 AM8/17/09
to sydney-google-...@googlegroups.com
On Sat, Aug 15, 2009 at 1:34 AM, .M.<modf...@gmail.com> wrote:
> Can I check the logic here with you all?
> Port WRS uses to communicate with local XMPP sever = 5275
Yes

> Port specified in run-server.sh - xmpp_server_port=5275
Yes

> Port XMPP servers use to communicate with each other  = 5269
Yes

As long as External Components is set to 5275 and Server to Server
Settings - 5269 then everything should be fine.
--
Harrison Conlin

David Banes

unread,
Aug 17, 2009, 4:13:26 AM8/17/09
to sydney-google-...@googlegroups.com
XMPP components/extensions can run on any available port, common
mistakes are to try and run multiple components on the same port,
forgetting to setup the hosts firewall for that port and
misconfiguring any shared secret between the server and the (remote)
component.

As I've introduced myself, I should say I'm happy to answer generic
XMPP questions for anyone on this list.

regards,

David.


David Banes
Director & CEO, Cleartext
Director & Secretary, Internet Industry Association
Director & Chairman, XMPP Standards Foundation
email: dba...@cleartext.com
xmpp: dba...@cleartext.com
web: http://cleartext.com
Tel: +61 2 8001 2600

- Cleartext is Carbon Minimised -
- Hosted standards based IM with Twitter support and archiving now
available.
--------------------------------------------------------------------------------------------------------
Email Filtering by Cleartext a Carbon Minimised company - www.cleartext.com
--------------------------------------------------------------------------------------------------------

.M.

unread,
Aug 18, 2009, 10:24:30 PM8/18/09
to Sydney Google Wave User Group

> As long as External Components is set to 5275 and Server to Server
Settings - 5269 then everything should be fine.

They are but still getting 404s (as per above message) from remote
servers when I try adding addresses.

There is definitely connectivity of some sort.

From warn log: 2009.08.19 01:57:19 Accepting self-signed certificate
of remote server: [*.wave.collaborynth.com.au]

But not sure about this error in error log

2009.08.19 01:57:24
[org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSession
(LocalOutgoingServerSession.java:258)] Error trying to connect to
remote server: au(DNS lookup: au:5269)

Any other suggestions?

I've retried remaking my certs and setting domain to rackandpin.com,
wave.rackandpin.com and checked that
I can connect remotely to rackandpin.com, wave.rackandpin.com,
wave.wave.rackandpin.com on 5269

My preference, and as originally set up, was to have rackandpin.com as
common name in cert, in XMPP config (xmpp.domain) and in run-server.sh
and leave the adding of wave hostname to the server.

Cheers
.M.
Reply all
Reply to author
Forward
0 new messages