No problem mate, glad to hear you solved it. > On 10 Sep 2020, at 01:20, Paul Whitney <paul.whitney@xxxxxxx> wrote: > > Thank you William for taking the time to reply. This thread/ticket can be closed. > > I started comparing packages with the failing LDAPS and to another that is working fine and discovered that one of the packages was older than the working one. So updated all of the packages and was able to pull the latest 389 packages needed. Then, I remove the existing config instance, reinstalled 389-admin and 389-adminutil, ran the setup and was able to successfully create the config instance and get dirsrv-admin to start. This wasnt an issue of TLS or ciphers, just that the admin serv could not bind to the config instance. Maybe synching the packages up with the right versions enable it to move past the post configuration steps. > > Again thank you for your time, — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
