• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    [SOLVED] fresh install "Handshake failed"

    Mango Automation Installation
    2
    4
    4.2k
    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.
    • mircsiczM
      mircsicz
      last edited by mircsicz

      Hi hi,

      I've just installed the enterprise eval version 3.3.2. First thing I did was upgrading to 3.3.3, after the upgrade I see the following error in the console:

      ERROR 2018-03-08T13:31:10,706 (org.springframework.web.socket.server.support.AbstractHandshakeHandler.handleInvalidUpgradeHeader:285) - Handshake failed due to invalid Upgrade header: null
      

      What happend, do I need to take any actions beside a "ma.sh restart"?

      EDIT: A "ma.sh restart" doesn't solve the problem

      1 Reply Last reply Reply Quote 0
      • mircsiczM
        mircsicz
        last edited by

        Seems it was an issue with my NginX Proxy. This is the setup that works now:

        server {
                listen          80;
                server_name  XXX.mydomain.de;
                return 301 https://$host$request_uri;
        }
        
        server {
                listen          443 ssl;
                server_name  XXX.mydomain.de;
                client_max_body_size 16M;
        
                ssl                     on;
                ssl_protocols           TLSv1.2;
                ssl_certificate         /etc/nginx/ssl/mydomain.de-bundle.crt;
                ssl_certificate_key     /etc/nginx/ssl/mydomain.de.key;
        
                proxy_cache off;
                proxy_store off;
        
                location / {
                        proxy_set_header Referer "";
                        proxy_pass http://10.xx.x.70:8080;
        #               proxy_redirect          off;
                        proxy_redirect          http://10.xx.x.70:8080 https://XXX.mydomain.de;
                        proxy_set_header        Host                    $host;
                        proxy_set_header        X-Real-IP               $remote_addr;
                        proxy_set_header        X-Forwarded-Host        $host;
                        proxy_set_header        X-Forwarded-Server      $host;
                        proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
                }
        }
        
        1 Reply Last reply Reply Quote 0
        • Jared WiltshireJ
          Jared Wiltshire
          last edited by

          Yep you have to be careful with proxies and websockets. That message is about a failed HTTP -> websocket upgrade. This is one of many reasons we recommend running HTTPS when using Mango over the internet.

          Developer at Radix IoT

          1 Reply Last reply Reply Quote 0
          • mircsiczM
            mircsicz
            last edited by

            That's why I'm proxying it, it's my lazy men's way to get it on HTTPS ;-)

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