Interesting follow up: Federating works great now, when I create a wave on collaborynth.com.au and add a wavesandbox participant, everything seems to go swimmingly.
However if I create a wave on wavesandbox and add a collaborynth.com.au I don't seem to have the ability to reply to the wave. I keep hitting the click here to reply to wave area but nothing happens. James On Wed, Oct 20, 2010 at 4:23 PM, James Purser <[email protected]>wrote: > And there's the secret sauce! > > Am now federating with the sandbox. > > Thanks for that. > > James > > > On Wed, Oct 20, 2010 at 4:04 PM, Soren Lassen <[email protected]> wrote: > >> Here's acmewave.com's prosody config: >> >> Host "*" >> component_ports = { 5275 } >> admins = { } >> modules_enabled = { >> "dialback"; >> "disco"; >> "ping"; >> "posix"; >> }; >> modules_disabled = { >> }; >> allow_registration = false; >> ssl = { >> key = "/etc/prosody/certs/localhost.key"; >> certificate = "/etc/prosody/certs/localhost.cert"; >> } >> log = { >> { levels = { min = "error" }, to = "file", filename = >> "/var/log/prosody/prosody.err" }; >> { levels = { min = "debug" }, to = "file", filename = >> "/var/log/prosody/prosody.log" }; >> } >> pidfile = "/var/run/prosody/prosody.pid" >> Host "localhost" >> Host "acmewave.com" >> enabled = true >> ssl = { >> key = "/etc/prosody/certs/example.com.key"; >> certificate = "/etc/prosody/certs/example.com.crt"; >> } >> Component "wave.acmewave.com" >> component_secret = <redacted> >> >> >> On Wed, Oct 20, 2010 at 1:44 PM, James Purser <[email protected]> >> wrote: >> > Okay, >> > I've redone the certs, I think I've got the prosody config correct and >> I've >> > already got the verification set to false and yet I still get the same >> > errors. >> > Would it be possible for you to post the acmewave prosody config? >> > Also is acmewave hosted internal or external to wavesandbox? >> > James >> > >> > On Wed, Oct 20, 2010 at 1:08 PM, Soren Lassen <[email protected]> wrote: >> >> >> >> FYI, I'm running acmewave.com and it's federating with wavesandbox.com >> >> fine, so I'm confident that wavesandbox.com federates. >> >> >> >> The acmewave.com cert was renewed last week and the wavesandbox.com >> >> cert was renewed last month. >> >> >> >> acmewave's run-config.sh has: >> >> WAVESERVER_DISABLE_VERIFICATION=false >> >> WAVESERVER_DISABLE_SIGNER_VERIFICATION=false >> >> >> >> I'm running prosody with tls disabled. >> >> >> >> -- >> >> 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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
