Hrmm I thought I had, I'll have another look. On Thu, Oct 14, 2010 at 6:17 PM, Anthony Baxter <[email protected]>wrote:
> Something is wrong with TLS. If you turn off TLS, it should work again. > > Anthony > > On Thu, Oct 14, 2010 at 17:37, James Purser <[email protected]> > wrote: > > Interesting I think I've tracked down why I'm not getting anywhere with > > federating. I think it might have something to do with my prosody setup: > > s2smanager debug First attempt to connect > to > > wavesandbox.com, starting with SRV lookup... > > adns debug Records for > > _xmpp-server._tcp.wavesandbox.com. already cached, using those... > > s2smanager debug wavesandbox.com has SRV > > records, handling... > > s2smanager debug Best record found, will > > connect to xmpp-server.l.google.com.:5268 > > adns debug Records for > > xmpp-server.l.google.com. already cached, using those... > > s2smanager debug DNS reply for > > xmpp-server.l.google.com. gives us 74.125.155.125 > > s2souta0c5378 info Beginning new connection > > attempt to wavesandbox.com (74.125.155.125:5268) > > s2souta0c5378 debug Connection attempt in > > progress... > > s2smanager debug DNS lookup for > > wavesandbox.com sent, waiting for response before we can connect > > s2smanager debug stanza [iq] queued until > > connection complete > > s2souta0c5378 debug > Received[s2sout_unauthed]: > > <features xmlns='http://etherx.jabber.org/streams'> > > wave.collaborynth.com.au:tls debug Received features > element > > s2souta0c5378 debug sending: <db:result > > from='wave.collaborynth.com.au' > > to='wavesandbox.com > '>fc061a8ab61d8874ff02967012f354570be9d9bf11ac9f9f2337d58b5256842e</db:result> > > s2souta1aba80 info sent dialback key on > > outgoing s2s stream > > s2souta1aba80 debug > Received[s2sout_unauthed]: > > <error xmlns='http://etherx.jabber.org/streams'> > > s2souta1aba80 debug </stream:stream> > > s2souta1aba80 debug sending: </stream:stream> > > socket debug server.lua: client > > 74.125.155.125:clientport read error: closed > > s2souta1aba80 info s2s disconnected: > > wave.collaborynth.com.au->wavesandbox.com (closed) > > s2souta1aba80 info Destroying outgoing > session > > wave.collaborynth.com.au->wavesandbox.com > > s2souta1aba80 info sending error replies for > 1 > > queued stanzas because of failed outgoing connection to wavesandbox.com > > stanzarouter debug Received[s2sin]: <iq > > id='Eq36DJOUySkAAAAAAAAABg==' type='error' to='wave.collaborynth.com.au' > > from='wavesandbox.com'> > > componentmanager debug iq stanza being handled > by > > component: wave.collaborynth.com.au > > socket debug server.lua: closed client > > handler and removed socket from list > > Note the error that is being returned: > > socket debug server.lua: client > > 74.125.155.125:clientport read error: closed > > Anyone else working with prosody at the moment? > > > > On Thu, Oct 14, 2010 at 5:26 PM, Soren Lassen <[email protected]> wrote: > >> > >> Sorry for the slow response. The certs for our acmewave.com instance > >> had expired and it took us a while to fix (the instructions at > >> http://www.waveprotocol.org/federation/certificates are horribly > >> broken and misleading, can someone who understands this stuff please > >> help fix them?) so we couldn't test it ourselves till now. > >> > >> I discovered one silly bug in RemoteWaveletContainerImpl which > >> prevented initiating contact from wavesandbox.com. The bug was fixed > >> just now in: > >> http://code.google.com/p/wave-protocol/source/detail?r=5276114aa6 > >> > >> With this fix I was able to successfully add acmewave.com > >> participants, including [email protected]. Unfortunately, echoey > >> only runs for a short while (a few minutes?) until it disconnects, as > >> reported in issue 110: > >> http://code.google.com/p/wave-protocol/issues/detail?id=110 > >> > >> We need a fix for that... > >> > >> Soren > >> > >> On Tue, Oct 5, 2010 at 2:28 PM, James Purser <[email protected]> > >> wrote: > >> > I've got collaborynth.com.au up and running but I have no idea if > it's > >> > federating properly. > >> > > >> > I have [email protected] running though I'm noticing issues > >> > with echoey and updating the web client. > >> > > >> > James > >> > > >> > On Tue, Oct 5, 2010 at 1:27 PM, Matt Richards <[email protected]> > >> > wrote: > >> >> While I've been testing Federation with sandbox, I am still getting > >> >> some > >> >> strange results. Is there another, more updated perhaps, server I can > >> >> test > >> >> with? Is there somebody I could collaborate with in real time, while > >> >> testing? Just want to make sure it not something on my end that is > >> >> causing > >> >> my issues with wavesandbox.com > >> >> Thanks > >> >> -- > >> >> --Matt > >> >> > >> >> -- > >> >> 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]<wave-protocol%[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]<wave-protocol%[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]<wave-protocol%[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]<wave-protocol%[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]<wave-protocol%[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.
