Re: [akka-user] Using remote actors with SSL results in dead letters

Hello, I got it to work, I found out that I could enable ssl-debugging in Java by using JAVA_OPTS. Which got me this log: https://gist.github.com/ekroth/ca8afe58253c2b7e22c1 [info] %% Initialized: [Session-1, SSL_NULL_WITH_NULL_NULL] [info] New I/O worker #4, fatal error: 40: no cipher suites

Re: [akka-user] Using remote actors with SSL results in dead letters

t the server before the client obviously. Here's the total output from client and server: server: https://gist.github.com/ekroth/db7279f02a99128b0440 client: https://gist.github.com/ekroth/0f47e6b28df194508092 Do you know of a working example of a SSL setup with Akka? Thanks On Thursday, 6 Feb

[akka-user] Using remote actors with SSL results in dead letters

://gist.github.com/ekroth/c564b572039d5f1b0fcd Output from akka (when sending): Client: [info] [DEBUG] [02/05/2014 20:58:40.145] [client-akka.remote.default-remote-dispatcher-5] [NettyTransport(akka://client)] SSL random number generator set to: AES128CounterSecureRNG [info] [DEBUG] [02/05/2014 20:58