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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
