This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Loxone webinterface and websocket

Hi

I am using the transparent webproxy with Sophos UTM 9.3.

When i try to access an Loxone(1) webinterface (Port 80) i can open the page and type in the credentials, but login is not possible.

Chrome debug says: 

WebSocket connection to 'ws://xxx.xxx.xxx.xxx/ws/' failed: Error during WebSocket handshake: Unexpected response code: 400

There are no errors or blocked pages in the proxy log. It just don't work.

Disabling the web proxy is the only cure. So i think it's an bug in the UTM web proxy. I can't contact the support, because i am an home user.

If an Sophos employee or forum mod want to test this for debugging, send me an PM/email so i can send you the website with the credentials.

(1) Loxone is an self hosted home automation server.



This thread was automatically locked due to age.
Parents
  • I have the same problem, just different server,  do you found a solution? 

    2017:08:10-23:53:22 utm httpproxy[7002]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="192.168.1.188" dstip="XXX.XXX.XXX.XXX" user="" group="" ad_domain="" statuscode="405" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="98" request="0x11847800" url="http://XXX.XXX.com/api/socket" referer="" error="" authtime="0" dnstime="35371" cattime="515" avscantime="8300" fullreqtime="150136" device="0" auth="0" ua="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36" exceptions="" category="9998" reputation="unverified" categoryname="Uncategorized" sandbox="-" content-type="text/xml"

    sophos UTM version: 9.502-4

  • This is more likely an error at XXX.XXX.com, Gustavo.  Here's what 405 means:

    405 Method Not Allowed

    A request was made of a resource using a request method not supported by that resource: for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

     

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • This is more likely an error at XXX.XXX.com, Gustavo.  Here's what 405 means:

    405 Method Not Allowed

    A request was made of a resource using a request method not supported by that resource: for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

     

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data