Clientless RDP access - websocket error

Recently I connected to Sophos portal and using clientless RDP access to my office computer, I got websocket error in chrome browser.

I tried IE , Edge, opera browser is also same error.

except Firefox 78.0.2, which is all right to use clientless RDP to my office computer. 

As I get through a sophos community, I can't find any solution. 

In chrome, I tried to inspect , it shows following error. (Even I added sophos applicance cert in my remote computer, I still got a same problems)

WebSocket connection to 'wss://x.x.x.x.:xxxx/screenmgr' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

Uncaught TypeError: Cannot read property 'options' of null
at Object.addOption (ui.js?t=1596862095:1079)
at Object.start (ui.js?t=1596862095:90)
at Object.WebUtil.initSettings (webutil.js:155)
at Object.load (ui.js?t=1596862095:45)
at window.onscriptsload (ui.js?t=1596862095:21)
at HTMLScriptElement.loadFunc (util.js?t=1596862095:407)

Please advise any other solution to fix it.

Thanks.

Parents
  • Hi  

    Any luck with deleting and creating clientless access again or with service restart via below command?

    #service clientless_access:restart -ds nosync

    Regards,

    Vishal Ranpariya
    Technical Account Manager | Sophos Technical Support

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link.

  • I tried deleting and creating clientless access, restart services, and reboot XG135.

    Still same websocket error in Chrome, IE, Opera

    But work in Firefox 78.0.2

    My XG135 Firmware version: XG135 (SFOS 17.5.12 MR-12)

    I am thinking to upgrade firmware, but I see a lot of post firmware 17.5.13 MR-13  and 18.0.1 MR-1 is not stable. Also 18.0 version is total different pic...

    It make me worry for those upgrade.

    Any other solution to solve this problem??

    Thanks

     

     

     

  • Hi  

    I would suggest to open a support case for further investigation on same.

    Regards,

    Vishal Ranpariya
    Technical Account Manager | Sophos Technical Support

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link.

  • Noted. thanks. 

    I checked the log of clientless access log in firewall, it shows following:-

    Aug 13 10:29:25 [4020]: INFO: Client 0: authenticated: user='edtrick'
    Aug 13 10:29:25 [4020]: INFO: Loading bookmark configuration: 'server'
    Aug 13 10:29:26 [4020]: INFO: starting session
    Aug 13 10:29:26 [4020]: INFO: Client 0: start screen requested: server
    Aug 13 10:29:26 [4020]: INFO: Loading bookmark configuration: 'server'
    Aug 13 10:29:26 [4020]: INFO: homedir /tmp/clientless/c962fmkb1bkbt9pg1eddcaeo7/4 setup ok
    Aug 13 10:29:29 [4020]: INFO: Client 0: connector started
    Aug 13 10:29:34 [4020]: INFO: Client 0: disconnected: Broken pipe
    Aug 13 10:30:04 [4020]: INFO: Client 0: connector stopped: 8

    Also for my datacentre firewall XG125, I also tested clientless , also got websocket error. 

    still checking and figure out client side or firewall problems..

     

Reply
  • Noted. thanks. 

    I checked the log of clientless access log in firewall, it shows following:-

    Aug 13 10:29:25 [4020]: INFO: Client 0: authenticated: user='edtrick'
    Aug 13 10:29:25 [4020]: INFO: Loading bookmark configuration: 'server'
    Aug 13 10:29:26 [4020]: INFO: starting session
    Aug 13 10:29:26 [4020]: INFO: Client 0: start screen requested: server
    Aug 13 10:29:26 [4020]: INFO: Loading bookmark configuration: 'server'
    Aug 13 10:29:26 [4020]: INFO: homedir /tmp/clientless/c962fmkb1bkbt9pg1eddcaeo7/4 setup ok
    Aug 13 10:29:29 [4020]: INFO: Client 0: connector started
    Aug 13 10:29:34 [4020]: INFO: Client 0: disconnected: Broken pipe
    Aug 13 10:30:04 [4020]: INFO: Client 0: connector stopped: 8

    Also for my datacentre firewall XG125, I also tested clientless , also got websocket error. 

    still checking and figure out client side or firewall problems..

     

Children