Ah, are you trying to run this behind the firewall? Federation won't
work in that
case. Both servers involved in federation need to be public facing, as
federation
uses XMPP dialback to establish communication between the servers.

   Thanks,
   -joe

On Fri, Jun 25, 2010 at 5:12 PM, Paul Carff <[email protected]> wrote:
> Please see the attached file.
> Cheers,
> Paul
>
>
>
> On Thu, Jun 24, 2010 at 9:17 AM, Joe Gregorio <[email protected]> wrote:
>>
>> What are you seeing on the console output from the running FedOne server?
>>
>>   Thanks,
>>   -joe
>>
>> --
>> Joe Gregorio
>> Developer Relations, Google Wave
>>
>>
>> On Mon, Jun 21, 2010 at 4:13 PM, pcarff <[email protected]> wrote:
>> > I have two machines able to federate with each other - all
>> > certificates seem to be good.  But I cannot connect to
>> > wavesandbox.com.
>> >
>> >
>> > On Jun 21, 11:22 am, pcarff <[email protected]> wrote:
>> >> My fedone server seems to be running fine, but I get the following
>> >> error when trying to federate with the wavesandbox:
>> >>
>> >> INFO: Could not discover remote JID: error_code: UNDEFINED_CONDITION
>> >>  for wavesandbox.com
>> >>
>> >> I look at the prosody log and see:
>> >>
>> >> Jun 21 11:12:12 jcp867c10       info    Incoming Jabber component
>> >> connection
>> >> Jun 21 11:12:12 wave.submarine.i.corp.google.com:component      info
>> >> Handling component auth
>> >> Jun 21 11:12:12 wave.submarine.i.corp.google.com:component      info
>> >> Component authenticated: wave.submarine.i.corp.google.com
>> >> Jun 21 11:12:12 wave.submarine.i.corp.google.com:component      info
>> >> Component successfully registered
>> >> Jun 21 11:13:01 s2sout880390    info    Beginning new connection
>> >> attempt to
>> >> wavesandbox.com (74.125.155.125:5268)
>> >> Jun 21 11:13:01 s2sout880390    info    sent dialback key on outgoing
>> >> s2s
>> >> stream
>> >> Jun 21 11:13:01 s2sout880390    info    s2s disconnected:
>> >> wave.submarine.i.corp.google.com->wavesandbox.com (closed)
>> >> Jun 21 11:13:01 s2sout880390    info    Destroying outgoing session
>> >> wave.submarine.i.corp.google.com->wavesandbox.com
>> >> Jun 21 11:13:01 s2sout880390    info    sending error replies for 1
>> >> queued
>> >> stanzas because of failed outgoing connection to wavesandbox.com
>> >> Jun 21 11:13:01 s2sout8995e0    info    Beginning new connection
>> >> attempt to
>> >> wavesandbox.com (74.125.155.125:5268)
>> >> Jun 21 11:13:01 s2sout8995e0    info    sent dialback key on outgoing
>> >> s2s
>> >> stream
>> >> Jun 21 11:13:01 s2sout8995e0    info    s2s disconnected:
>> >> wave.submarine.i.corp.google.com->wavesandbox.com (closed)
>> >> Jun 21 11:13:01 s2sout8995e0    info    Destroying outgoing session
>> >> wave.submarine.i.corp.google.com->wavesandbox.com
>> >> Jun 21 11:13:01 s2sout8995e0    info    sending error replies for 1
>> >> queued
>> >> stanzas because of failed outgoing connection to wavesandbox.com
>> >> Jun 21 11:13:01 s2sout8a2720    info    Beginning new connection
>> >> attempt to
>> >> wave.wavesandbox.com (74.125.155.125:5268)
>> >> Jun 21 11:13:01 s2sout8a2720    info    sent dialback key on outgoing
>> >> s2s
>> >> stream
>> >> Jun 21 11:13:01 s2sout8a2720    info    Destroying outgoing session
>> >> wave.submarine.i.corp.google.com->wave.wavesandbox.com
>> >> Jun 21 11:13:01 s2sout8a2720    info    sending error replies for 1
>> >> queued
>> >> stanzas because of failed outgoing connection to wave.wavesandbox.c
>> >> om
>> >> Jun 21 11:13:01 xmppserver_listener     info    s2s disconnected:
>> >> nil->nil
>> >> (closed)
>> >> Jun 21 11:13:01 s2smanager      info    Destroying nil session nil->nil
>> >>
>> >> Thoughts?
>> >>
>> >> Cheers,
>> >> Paul
>> >
>> > --
>> > 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.
>

-- 
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.

Reply via email to