Bug 6098 - Web Access disconnects with "unknown message type"
Summary: Web Access disconnects with "unknown message type"
Status: CLOSED WORKSFORME
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.16.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-24 08:08 CET by Pierre Ossman
Modified: 2023-08-29 13:34 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2016-11-24 08:08:58 CET
The HTML seems to be getting some protocol stuff screwed up in some cases and gets thrown out by the server with this error:

>  Connections: closed: 127.0.0.1::58200 (unknown message type)

Not sure what the triggering condition is at this point.
Comment 1 Samuel Mannehed cendio 2017-02-08 14:13:41 CET
Sometimes get this as well:

> Uncaught RangeError: Invalid typed array length
>     at new Uint8Array (native)
>     at RFB._negotiate_server_init (https://eudemo.thinlinc.com:300/include/rfb.js:911:30)
>     at RFB._init_msg (https://eudemo.thinlinc.com:300/include/rfb.js:1041:33)
> util.js:220  Msg: Unsupported tight subencoding received, filter: 255
> Util.Error @ util.js:220
Comment 2 Samuel Mannehed cendio 2017-10-24 16:28:47 CEST
Today Web Access disconnected after a few seconds of simply showing the profile chooser. The xinit.log showed:

> unknown message type 80
>
> Tue Oct 24 15:30:14 2017
>  VNCSConnST:  tl-shadow-notify: CloseAuthenticatedConnection
>  Connections: closed: 127.0.0.1::38480 (unknown message type)

Could not reproduce multiple times.
Comment 3 Pierre Ossman cendio 2023-08-29 13:34:42 CEST
We've not seen this occur again in years, so let's assume it got fixed somewhere along the way.

Note You need to log in before you can comment on or make changes to this bug.