Resolved. Regenerated the private key and certificate... seems to work fine.
This issue may have initially occurred because I opened OpenSSL to generate the key and certificate rather than using the command prompt to run openssl. On Oct 4, 4:45 pm, Ben Kalman <[email protected]> wrote: > This could be caused by a corrupt private key or certificate. > > Guice needs a WaveSigner, so asks WaveSignerProvider for one (throgh the > get() method), which in turn reads the private key and certificate from the > files specified in the configuration file. If it fails, it can't provide a > WaveSigner and hence the "could not make wave signer" error. For the > record, if the files were missing there would be a different error ("could > not read x") but it amounts to the same thing. > > -- Ben > > On Mon, Oct 5, 2009 at 3:39 AM, Anon _ <[email protected]>wrote: > > > > > When I run the run-server file, the installation hangs. I receive a > > message after "wave_disable_signer_verification" which reads: > > > "guice provision errors: 1) could not make wave signer" ... followed > > by a full page of code. > > > Can anyone describe what is occurring or suggest a correction? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
