ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ManageEngine ADSelfService

    IT Discussion
    4
    5
    361
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • GreyG
      Grey
      last edited by Grey

      The cert expired and every time I use their documentation (https://download.manageengine.com/products/self-service-password/adselfservice-plus-ssl-installation-guide.pdf) for installing a new one using a .cer file, it locks the tomcat or something since the pages don't load despite the port being open in nmap and the service running. Logs even state that everything started ok. It all goes sideways (ERR_CONNECTION_REFUSED) after a replace the selfservice.keystore file and restart the service.

      Has anyone else done a successful cert replacement when the old one goes out of date?

      dbeatoD 1 Reply Last reply Reply Quote 1
      • dbeatoD
        dbeato @Grey
        last edited by

        @Grey I have been placing the Manage Engine Systems behind a SSL Proxy to make it easier and automated these days.

        1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch
          last edited by

          Same here. Mines behind a reverse proxy because their tomcat server or whatever sucks.

          I only use ServiceDesk.

          1 Reply Last reply Reply Quote 0
          • jt1001001J
            jt1001001
            last edited by

            We use ServiceDesk at work for ticketing never was able to get SSL to work, gave up and put it behind our Kemp load balancer/reverse proxy

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @jt1001001
              last edited by

              @jt1001001 said in ManageEngine ADSelfService:

              We use ServiceDesk at work for ticketing never was able to get SSL to work, gave up and put it behind our Kemp load balancer/reverse proxy

              I originally had ServiceDesk working with an imported GoDaddy certificate, no issues.

              But there was no good way to do it with Let's Encrypt when I moved to that. Also, I really needed the Reverse Proxy anyway.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post