Hi, When I start a new wave or try to reply to an existing wave on wavesandbox, I get the following error message in my FedOne logs.. I know so much, I've tried to create waves and federate with various certificate, perhaps is the sandbox using an old certificate? I'm able to create new waves on my FedOne, and they appear on the sandbox, however if I try to resume one later or add myself (or echoey to a wave) I get this.
<iq type="get" to="wave.eggy.cc" from="wave.wavesandbox.com" id="46b32f84-getsigner.262-gs"> <pubsub xmlns="http://jabber.org/protocol/pubsub"> <items node="signer"> <signer-request xmlns="http://waveprotocol.org/protocol/0.2/ waveserver" signer-id="ca6g3MvlJ1PbEnjH8OVP/Bgr4UL1LA4Gir6jnQ14VxI=" history-hash="aUEo4J0wUfuZVfnEchxpcoD5Mow=" version="6" wavelet- name="wave://eggy.cc/w+dNC8eiesppbT/conv+root"/> </items> </pubsub> </iq> Nov 14, 2009 6:24:17 AM org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent processIqPacket INFO: key for this error is org.xmpp.packet.IQ:wave.wavesandbox.com: 46b32f84-getsigner.262-gs Nov 14, 2009 6:24:17 AM org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl getDeltaSignerInfo SEVERE: incoming getDeltaSignerInfo: cannot find signer info for signed delta (breach of contract!) I've also noted, that I'll get a nasty refresh this page error message on the wavesandbox once I add echoey into a wave on there, does the echoey agent work? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
