Would anyone try to connect to my xmpp on wave.wavenation.eu? Perhaps send me a wave at [email protected]
Kind regards Christoffer Hallas On Wed, Sep 2, 2009 at 5:18 PM, Christoffer Hallas Pedersen < [email protected]> wrote: > I do have Openfire up and running. But I can only start up Wave FedOne when > the hosts is set. Very odd indeed. Only then will it start, and succesfully > register as a component with Openfire. > What do I have to do, to allow it to bind on my domain? > > Maybe I forgot to map the XMPP port. > > Let me see. > > > On Wed, Sep 2, 2009 at 3:28 PM, Sam Thorogood <[email protected]>wrote: > >> >> > Is it correct that, in order to bind the server, I have to add the >> > entry to my /etc/hosts file? >> > >> > 127.0.0.1 wave-example.com >> > >> > Unless I do this, the /run-server.sh is unable to bind to the address. >> >> No way. Your Openfire instance (I presume) won't appreciate this at >> all. I'm actually a little confused - you say that you have two >> clients talking together - which is great. Do you have an XMPP server >> up and running? The reference implementation is configured to register >> itself as a component of a standards-compliant XMPP server. >> >> It doesn't open a port for this, it dials up ${XMPP_SERVER_HOSTNAME} >> on ${XMPP_SERVER_PORT} (defined in 'run-config.sh.example', which you >> should have copied to 'run-config.sh'). >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
