More progress on this side, I can now see the first "message" sent, but anything after that times out. Is there some port, or range of ports I need to open on my firewall that I've missed? I've opened the two wave related ports in the run-config.sh, and all ports ejabberd is using..
On Sat, Oct 2, 2010 at 7:50 PM, Matt Richards <[email protected]> wrote: > I've disabled TLS (breaking a few things) and I still get timeouts when > trying this with wavesandbox. > James is your server still up? > > > On Sat, Sep 18, 2010 at 8:39 PM, James Purser <[email protected]>wrote: > >> If it helps for testing, I've turned on [email protected] >> >> At least if we can baseline a couple of fedone instances talking to >> each other we can ensure that somethings working. >> >> James >> >> On Sep 18, 1:31 pm, Matt Richards <[email protected]> wrote: >> > I'm still getting time outs when I try to Federate with WaveSandbox.com >> :( >> > >> > On Fri, Sep 17, 2010 at 8:55 AM, James Purser <[email protected] >> >wrote: >> > >> > >> > >> > >> > >> > > Just one other question, does WiaB still do the ping thing? >> > >> > > I'm not seeing any attempt to ping anything that I put in the config >> file. >> > >> > > On Fri, Sep 17, 2010 at 11:28 PM, James Purser < >> [email protected]> >> > > wrote: >> > > > Okay looks like I've got the same expired cert issue. Will >> regenerate >> > > > tomorrow and test again >> > >> > > > On Fri, Sep 17, 2010 at 11:15 PM, James Purser < >> [email protected]> >> > > wrote: >> > > >> No, let me try that >> > >> > > >> On Fri, Sep 17, 2010 at 11:10 PM, Anthony Baxter >> > > >> <[email protected]> wrote: >> > > >>> Did you turn off TLS? >> > >> > > >>> On Sep 17, 2010 11:05 PM, "James Purser" <[email protected]> >> > > wrote: >> > > >>>> Hrmm, >> > >> > > >>>> I'm still getting disco timeouts. >> > >> > > >>>> James >> > >> > > >>>> On Fri, Sep 17, 2010 at 3:15 PM, Soren Lassen <[email protected]> >> > > wrote: >> > > >>>>> On Sep 16, 5:54 pm, Anthony Baxter <[email protected]> >> wrote: >> > > >>>>>> So things have changed on the Google XMPP servers. They appear >> to >> > > have >> > > >>>>>> some TLS support, but in a not-entirely >> > > working-that-I-can-understand >> > > >>>>>> way. I had to edit my prosody.cfg.lua and turn *off* TLS to get >> > > >>>>>> prosody to successfully complete the disco dance with >> > > wavesandbox.com. >> > > >>>>>> That got me a bit closer, but it turns out that the wave >> signing >> > > >>>>>> certificate for wavesandbox.com recently expired. We're >> working to >> > > >>>>>> deploy a new version of this certificate into production. >> > >> > > >>>>> The new version was deployed 6 hours ago. Please let us know if >> you >> > > >>>>> continue to experience problems federating with wavesandbox.com >> . >> > >> > > >>>>> We are still working through some problems with the >> acmewave.com and >> > > >>>>> initech-corp.com instances. The cert for initech-corp.com also >> > > >>>>> expired. We'll get a new one next week. >> > >> > > >>>>> Soren >> > >> > > >>>>> -- >> > > >>>>> 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]> >> <wave-protocol%2bunsubscr...@goog legroups.com> >> > > . >> > > >>>>> 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]> >> <wave-protocol%2bunsubscr...@goog legroups.com> >> > > . >> > > >>>> 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]> >> <wave-protocol%2bunsubscr...@goog legroups.com> >> > > . >> > > >>> 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]> >> <wave-protocol%2bunsubscr...@goog legroups.com> >> > > . >> > > For more options, visit this group at >> > >http://groups.google.com/group/wave-protocol?hl=en. >> > >> > -- >> > --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. >> >> > > > -- > --Matt > -- --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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
