Re: [389-users] Problems with SSL
Ski Kacoroski wrote:
Ok, looks like I need to reboot the entire server to get the admin
console stop server functionality to work.
You probably could have just restarted
the directory server and admin
server:
service dirsrv restart
service dirsrv-admin restart
Now, has anyone had any luck
using a * cert with the 389 server?
What problems are you having still?
cheers,
ski
On 03/02/2010 03:24 PM, Ski Kacoroski wrote:
> Hi,
>
> I am having problems with SSL setup. First I tried via the admin
> console to use our company's star cert, but no matter what [in/password
> I picked for the keystore, when I tried to restart the server it would
> not accept my pin/password that I had just entered. I then gave up and
> ran the setupssl2.sh script and this worked except that it threw an
> error when trying to modify the directory to turn on ssl. So I went in
> via the admin console and was able to turn on ssl for the admin console
> and my directory. The problem now is that I cannot stop the server from
> the admin console (I can start it ok). I just get a dialog with
> "Directory Server nsd-org could not be stopped". Any ideas on why when
> I can start the server ok? Also has any one else made this work with a
> star cert?
>
> cheers,
>
> ski
>
>