View Single Post
Posts: 882 | Thanked: 1,310 times | Joined on Mar 2007
#467
Originally Posted by gs1 View Post
It works brilliantly unsecured inside my LAN but I'm having problems getting SSL to work on the client and would really appreciate some help.

I set up SSL and the remote discovery account via the server as described on the Wiki and am forwarding 1978, and the range 19780 to 19785. On the N900 I can access the server via the browser after logging in, and I can stream video using the Browser profile (choppy, but I haven't played with any of the data rate settings). That makes me think the server is set up correctly?

When I go to the client I can successfully enable Remote Discovery but can't connect to the server. Connect automatically gives "not connected to server". If I try to connect manually, put in the same address that worked in the browser: mycurrent_IP:1978 and select SSL I get the same thing whereas I was expecting some sort of log in password request.

Any ideas appreciated,
Geoff
If you trust just basic auth, you can disable ssl and use "force authentication" to enable basic auth without encryption. That should make it work out of box. But if you want ssl, you need to install the custom libsoup package listed in the wiki (if you are using an N900). I can't promise you that it doesn't mess up other apps using the libsoup library, but I didn't see any ill effects when I tried it.
 

The Following 2 Users Say Thank You to ukki For This Useful Post: