No announcement yet.

Can't log in to Mirth Connect Administrator 3.1.1- SSLHandshake Exception

  • Filter
  • Time
  • Show
Clear All
new posts

  • Can't log in to Mirth Connect Administrator 3.1.1- SSLHandshake Exception

    I have Mirth 3.1.1 installed on a Windows 2012 R2 server and am having no problems with my active channel receiving HL7 messages and routing them to their expected destinations, but attempting to log in to the Mirth Connect Administrator fails whether I'm connecting from my desktop machine or locally on the server. Both the server and every client machine I've used are running Java 8u25. The most recent updates to the server were applied on 12/17, and as recently as the morning of 12/22 I was still able to get logged in but sometime in the afternoon this behavior started. I've tried clearing my Java cache multiple times, both on the client machine and on the server, but to no avail. I can connect to the server using both telnet and remote desktop, and I can get the main launch page to come up at http://mirth.intranet.local:8080. when I try to navigate to the "Access Secure Site" URL, I receive errors similar to the one below from Chrome.
    "The webpage at https://mirth.intranet.local:9443/webadmin/Index.action might be temporarily down or it may have moved permanently to a new web address.

    Each attempt to log in to the Administrator results in the message "There was an error connecting to the server at the specified address. Please verify that the server is up and running". The server was originally installed using port 8443 for the admin, but in searching the forum for a solution before posting I saw a related thread that suggested changing the port # to see if that changed the behavior. In this case, it didn't. I've also noticed that in the config there seem to be a significant number of protocols and ciphers listed by default, should some of those be removed/disabled?

    Stack trace appears below. Has anyone experienced something similar to this? Thanks!
    Code: No appropriate protocol
                    at Source)
                    at Source)
                    at Source)
                    at Source)
                    at Source)
                    at org.eclipse.jetty.http.HttpParser.fill(
                    at org.eclipse.jetty.http.HttpParser.parseNext(
                    at org.eclipse.jetty.http.HttpParser.parseAvailable(
                    at org.eclipse.jetty.server.AsyncHttpConnection.handle(
                    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
                    at org.eclipse.jetty.util.thread.QueuedThreadPool$
                    at Source)
    DEBUG 2014-12-23 12:44:00,599 [qtp2142750150-36] close [email protected]{l(/<->r(/,d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0!}-{[email protected] SSL NEED_WRAP i/o/u=215/0/0 ishut=false oshut=false {[email protected],g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}}
    DEBUG 2014-12-23 12:44:00,599 [qtp2142750150-32 Selector0] destroyEndPoint [email protected]{l(null)<->r(,d=true,open=false,ishut=true,oshut=true,rb=false,wb=false,w=true,i=0!}-{[email protected] SSL NEED_WRAP i/o/u=215/0/0 ishut=false oshut=false {[email protected],g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}}
    DEBUG 2014-12-23 12:44:00,599 [qtp2142750150-32 Selector0] org.eclipse.jetty.server.AbstractHttpConnection: closed [email protected],g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0
    DEBUG 2014-12-23 12:44:00,631 [qtp2142750150-32 Selector0] created [email protected]{l(/<->r(/,d=false,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0}-{[email protected] SSL NOT_HANDSHAKING i/o/u=-1/-1/-1 ishut=false oshut=false {[email protected],g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}}
    Last edited by bschwartz; 12-23-2014, 12:12 PM. Reason: added mention of cleared Java cache.

  • #2
    We disabled SSLv3 as a protocol in 3.1.1. For some reason your Administrator and Server cannot find a common protocol that they both support. You can first try adding SSLv3 back to the client and server protocols and see if that fixes your issues. Then you can determine why they may not be supporting other protocols.

    See our upgrade guide for some more information


    • #3
      Try updating the client protocols in to

      https.client.protocols = TLSv1

      then restart the Mirth Connect Server and try again.

      If that doesn't work please indicate what your https.client.protocol and https.server.protocols settings are


      • #4
        I am having ERR_CONNECTION_CLOSED problem while visiting


        • #5
          I am Having ERR_CONNECTION_CLOSED problem in my PC.

          Here’s the mail I got recently for my problem
          I have the same issue as Jeffrey.e.Lamb and I think your reply misses a key point. I want to turn Activity Reporting ON, but leave Web Filtering OFF as (for now) I only want to monitor sites my children use.
          But even with Web Filtering set to OFF, I get an "ERR_CONNECTION_CLOSED" error from Chrome trying to open and other https sites - I have to change from Child to Standard account or disable Family Safety altogether for it to work. This seems pretty useless.
          Strangely IE11 tells me that has an invalid security certificate, rather than block access.

          Or otherwise try this: