Announcement

Collapse
No announcement yet.

Error 404 - Not Found on HTTPS Port 8443

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error 404 - Not Found on HTTPS Port 8443

    When I upgraded to Mirth 1.7.0.3285, on Linux and Solaris 10, I receive an errorwhen trying to connect to the web based mirth administrator via https on port 8443;

    The 'wrapper.log' contains;
    Code:
    STATUS | wrapper  | 2008/02/02 11:55:19 | --> Wrapper Started as Daemon
    STATUS | wrapper  | 2008/02/02 11:55:20 | Launching a JVM...
    INFO   | jvm 1    | 2008/02/02 11:55:20 | Wrapper (Version 3.2.3) [url]http://wrapper.tanukisoftware.org[/url]
    INFO   | jvm 1    | 2008/02/02 11:55:20 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
    INFO   | jvm 1    | 2008/02/02 11:55:20 |
    INFO   | jvm 1    | 2008/02/02 11:55:27 | Mirth 1.7.0.3285 (January 28, 2008) server successfully started: Sat Feb 02 11:55:26 CST 2008
    INFO   | jvm 1    | 2008/02/02 11:55:27 | This product includes software developed by SymphonySoft Limited ([url]http://www.symphonysoft.com[/url]) and its contributors.
    INFO   | jvm 1    | 2008/02/02 11:55:27 | Running Java 1.6.0_03 on Linux (2.6.23.14-107.fc8, i386)
    and the web output when connecting to localhost on port 8443 displays;
    Code:
    Error 404 - Not Found.
    No context on this server matched or handled this request.
    Contexts known to this server are:
    
        * HttpContext[/,/]
    
    The links above may not work if a virtual host is configured
    If I rollback to mirth-1.7.0.3207, there are no such issues

  • #2
    Re:Error 404 - Not Found on HTTPS Port 8443

    Are you trying to launch the administrator? Launch using 8080 - it will still use HTTPS and 8443 to communicate once the administrator is loaded.
    Chris Lang

    Comment


    • #3
      Re:Error 404 - Not Found on HTTPS Port 8443

      Thanks for the response to my query Chris. Connecting via HTTP on port 8080 gave me access to the the web page that has the Mirth Administrator launch button in version 1.7.0.3285.

      Am I to assume that the web connection via HTTPS on port 8443 is no longer the web access method for version 1.7

      Post edited by: gturrill, at: 02/02/2008 03:40

      Comment


      • #4
        Re:Error 404 - Not Found on HTTPS Port 8443

        Correct - 8443 was never officially supported but worked due to a bug. We fixed the bug and 8080 is the only available launch point.
        Chris Lang

        Comment


        • #5
          Re:Error 404 - Not Found on HTTPS Port 8443

          can this be modified through a config script? I am trying to run two mirth instances in parallel so that I can check out the differences between 1.7.1 and 1.8.0. Based on the source code, it looks like 1.8 supports a lot of features I would like. I dug around in the conf dir and a number of the 1.8 xml files but didn't see anything that jumped out at me and said "edit this to change the port through which mirth will be accessed by the Mirth Administrator.

          details after some more digging

          Code:
          lsof -i TCP:8080
          COMMAND   PID      USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
          java    22285 jensweber    8u  IPv6 0xb55719c      0t0  TCP *:http-alt (LISTEN)
          
          ps -x (abbreviated)
          22285 ttys000    8:32.66 /usr/bin/java -Xmx256m -classpath mirth-launcher.jar:lib/log4j-1.2.13.jar:conf/ com.webreach.mirth.server.launcher.MirthLauncher mirth-launcher.xml
          
          lsof -i TCP:8081
          
          http.port=8080 from mirth 1.7.1 mirth.properties
          http.port=8081 from mirth 1.8.0.4014 mirth.properties
          
          exception when trying to run mirth 1.8.0.4014 mirth.sh while mirth 1.7.1 is running
          
          WARN  2008-12-17 05:25:42,983 [Thread-0] org.mortbay.util.ThreadedServer: Failed to start: [email protected]:8443
          WARN  2008-12-17 05:25:42,986 [Thread-0] com.webreach.mirth.server.Mirth: Could not start web server.
          org.mortbay.util.MultiException[java.net.BindException: Address already in use]
          	at org.mortbay.http.HttpServer.doStart(HttpServer.java:686)
          	at org.mortbay.util.Container.start(Container.java:72)
          	at com.webreach.mirth.server.Mirth.startWebServer(Mirth.java:389)
          	at com.webreach.mirth.server.Mirth.startup(Mirth.java:153)
          	at com.webreach.mirth.server.Mirth.run(Mirth.java:118)
          java.net.BindException: Address already in use
          	at java.net.PlainSocketImpl.socketBind(Native Method)
          	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
          	at java.net.ServerSocket.bind(ServerSocket.java:319)
          	at java.net.ServerSocket.<init>(ServerSocket.java:185)
          	at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:106)
          	at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:106)
          	at com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:71)
          	at org.mortbay.http.SslListener.newServerSocket(SslListener.java:291)
          	at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
          	at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:503)
          	at org.mortbay.http.SocketListener.start(SocketListener.java:203)
          	at org.mortbay.http.HttpServer.doStart(HttpServer.java:716)
          	at org.mortbay.util.Container.start(Container.java:72)
          	at com.webreach.mirth.server.Mirth.startWebServer(Mirth.java:389)
          	at com.webreach.mirth.server.Mirth.startup(Mirth.java:153)
          	at com.webreach.mirth.server.Mirth.run(Mirth.java:118)
          Mirth 1.8.0.4014 (November 14, 2008) server successfully started: Wed Dec 17 05:25:52 PST 2008
          This product was developed by WebReach, Inc. ([url]http://www.webreachinc.com[/url]) and its contributors (c)2005-2008.
          Running Java 1.5.0_16 on Mac OS X (10.5.5, i386) with charset MacRoman.
          Mule uses the next default ports, which should be free in the server. The ports are:

          *
          HTTP port, default 8080, set at conf/mirth.properties, at http.port propperty.
          *
          HTTPS port, default 8443, set at conf/mirth.properties, at https.port property.
          from - http://www.mirthproject.org/index.ph...4&id=confmirth
          Why would this still be failing after I changed the config file to bind 8081 - a free port for the webserver? Is there something else i should have done or am I misunderstanding something?

          Thanks
          Fieran

          Post edited by: fmason, at: 12/17/2008 05:49

          Post edited by: fmason, at: 12/17/2008 07:22
          Fieran Mason-Blakley
          Standards Researcher
          Genologics Life Sciences

          Comment


          • #6
            Resolved

            the problem was not with 8080 but with 8443
            that is, the server was able to bind 8081 for http service, but was not able to bind 8443 for https service. I provided 8444 for https service and that resolved the error
            Fieran Mason-Blakley
            Standards Researcher
            Genologics Life Sciences

            Comment

            Working...
            X