This has started happening for me recently after a Chrome upgrade. I am seeing this on 1.0.0, with websockets configured. *NOT* seeing it on 0.9.14 without websockets. Has been working fine on 1.0.0 w/ websockets previously.
Experiencing error with these browser versions: (Linux) Google Chrome Version 73.0.3683.86 (Official Build) (64-bit) Brave Version 0.61.52 Chromium: 73.0.3683.86 (Official Build) (64-bit) Chromium Version 73.0.3683.75 (Official Build) Built on Ubuntu , running on LinuxMint 19.1 (64-bit) (Windows) Chrome 73 (not in front of it at the moment) Working *correctly* in: (Firefox, Edge) Slimjet Version 22.0.4.0 (based on Chromium 72.0.3626.121) (Official Build) (64-bit) -Jonathan Hankins On Mon, Apr 1, 2019 at 1:19 PM Nick Couchman <vn...@apache.org> wrote: > On Mon, Apr 1, 2019 at 1:33 PM elvelux <os...@lantalde.net> wrote: > >> I have recently discovered that the error only occurs connecting by >> https, no >> by http. >> >> > I use Guacamole 1.0.0 with Chrome and HTTPS routinely with no issues. > > -Nick > -- ------------------------------------------------------------------------ Jonathan Hankins Homewood City Schools jhank...@homewood.k12.al.us ------------------------------------------------------------------------ -- This e-mail is intended only for the recipient and may contain confidential or proprietary information. If you are not the intended recipient, the review, distribution, duplication or retention of this message and its attachments is prohibited. Please notify the sender of this error immediately by reply e-mail, and permanently delete this message and its attachments in any form in which they may have been preserved.
