The DNS issue will only bite if you have multiple SRV (or A) records. I'm not sure what the problem would be - personally, I find Prosody's logging (at debug level) to be more useful for debugging this than Openfire's, which can be a little obscure. Have a look at the Openfire logs, though (you'll probably need the most detailed logs) and see why the 2 servers can't talk to each other. It sounds like the XMPP servers don't like each other for some reason.
On Tue, May 4, 2010 at 10:25, Paul Carff <[email protected]> wrote: > I have two servers set up that I can get to work individually (using > Openfire on each). The dig ... command referenced in the documentation > resolves both wave domains properly. But I cannot get them to communicate > to each other. Is the DNS issue with Openfire a likely culprit? Any > work arounds suggested? > Cheers, > Paul > > > > On Mon, May 3, 2010 at 5:08 PM, Anthony Baxter <[email protected]> > wrote: >> >> That suggests you haven't configured the component on the xmpp server and >> wave server to match. Check the configuration docs again. Note also the big >> warning at the top about a bug in the current released version of openfire's >> DNS. >> >> On May 4, 2010 8:28 AM, "cowgod" <[email protected]> wrote: >> > i'm trying to setup an internal wave server where i work. i chose to >> > use openfire as the xmpp server, and i'm installing it and the wave- >> > protocol on the same server (debian 5). the xmpp side of things seems >> > to be setup just fine and i have configured the external component >> > settings as specified in the documentation. >> > >> > when i attempt to start the wave server with ./run-server.sh, i get >> > the following info: >> > May 3, 2010 2:53:10 PM >> > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl <init> >> > INFO: Wave Server configured to host local domains: [wave.example.com] >> > couldn't connect to XMPP server:org.xmpp.component.ComponentException: >> > host-unknown >> > >> > wave.example.com is of course configured for my company domain. when >> > i attempt to browse to wave.example.com in my browser, nothing gets >> > served. >> > >> > is this just a firewall issue? the doumentation doesn't really give a >> > good overview of which ports are for what protocol and what needs to >> > be opened. i'd love some help because i really want to be able to use >> > wave for our internal company communication. >> > >> > -- >> > 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. >> > >> >> -- >> 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. > > -- > 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. > -- Anthony Baxter, [email protected] -- 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.
