Under the assumption that Tomcat has issues with it's HTTPS connector vs. WebSocket, I'd recommend switching things over to using a reverse proxy like Apache or Nginx for SSL termination. If the problem is the same as the issue referenced in the mailing list thread I mentioned earlier, that should resolve this.
Though Tomcat provides some documentation on WebSocket-related configuration [1], and it does mention SSL, just using a proxy for SSL termination may be the easiest solution here: http://guacamole.apache.org/doc/gug/proxying-guacamole.html - Mike [1] https://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html On Mon, Jan 8, 2018 at 1:03 PM, Adrian Owen <[email protected]> wrote: > Hi Mike, > > > > Yes Chrome shows this error: > > > > The key "target-densitydpi" is not supported. > > angular.js:11699 TypeError: Cannot read property 'guac-full-name' of > undefined > > at app.js?v=0.9.13-incubating:293 > > at angular.js:9442 > > at angular.js:13292 > > at m.$eval (angular.js:14547) > > at m.$digest (angular.js:14363) > > at m.$apply (angular.js:14652) > > at l (angular.js:9734) > > at P (angular.js:9924) > > at XMLHttpRequest.H.onload (angular.js:9865) > > (anonymous) @ angular.js:11699 > > app.js?v=0.9.13-incubating:129 WebSocket connection to > 'wss://192.168.242.88:9943/guacamole/websocket-tunnel?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F&GUAC_DATA_SOURCE=json&GUAC_ID=RDP%20wensan%40SERLOCDEV12%20localadmin%40SERHUBSMTP01%20SERHUBSMTP01&GUAC_TYPE=c&GUAC_WIDTH=800&GUAC_HEIGHT=600&GUAC_DPI=96&GUAC_AUDIO=audio%2FL8&GUAC_AUDIO=audio%2FL16&GUAC_IMAGE=image%2Fjpeg&GUAC_IMAGE=image%2Fpng&GUAC_IMAGE=image%2Fwebp' > failed: Error during WebSocket handshake: Unexpected response code: 404 > > connect @ app.js?v=0.9.13-incubating:129 > > :9943/guacamole/api/session/tunnels/1c5b44cb-1a56-45c4-9890-737f7be708bd/activeConnection/connection/sharingProfiles?token=5A4E4579D2378423604D5D90DF3CA7302AC998063E095D41768D428762B8E09F > Failed to load resource: the server responded with a status of 404 (Not > Found) > > > > Adrian > > > > From: Mike Jumper [mailto:[email protected]] > Sent: 08 January 2018 20:47 > To: [email protected] > Subject: Re: SSL RDP Download file fails > > > > On Mon, Jan 8, 2018 at 12:44 PM, Mike Jumper <[email protected]> > wrote: > > Do you see anything in the network tab of your browser's dev tools when the > upload fails? If Tomcat is rejecting the request, the response within the > network tab may reveal the cause. Depending on whether IE successfully logs > such things, you may need to switch to a different browser to obtain the > necessary information. > > > > > > It might also be interesting to check whether WebSocket is failing when > Tomcat is configured for HTTPS. There was another thread on this list > recently which dealt with printing not working if the HTTP tunnel was in > use. As file transfer goes over the same underlying mechanism as printing, > this could cause what you're seeing. > > > > https://lists.apache.org/thread.html/ae6a8a0c8bfe1a5a84aad779a3b594855e408f78ce20dc6f1b5da4ad@%3Cuser.guacamole.apache.org%3E > > > > - Mike > >
