Hi Nick, We gave up on IIS Url Rewrite. The error persisted no matter what we tried.
In the end we wrote ASP.NET Core reverse Proxy using ProxyKit. https://github.com/damianh/ProxyKit Our custom site supports all browsers. Works perfectly. Thanks, Adrian From: Nick Couchman [mailto:[email protected]] Sent: 27 September 2019 15:13 To: [email protected] Subject: Re: Guacamole IIS URL Rewrite Chrome FAILS On Fri, Sep 27, 2019 at 5:57 AM Adrian Owen <[email protected]<mailto:[email protected]>> wrote: Hi Nick, “Can Chrome access anything on that IIS web server? Do other pages hosted by that server work, and only Guacamole fails?” Yes. All other pages work fine, I can go to NGINX landing page, and Guacamole home page. It is only when session starts. Only IE 11 works. The old Edge browser worked but the new Edge browser built on chromium fails. I suspect that Websockets is to blame, here - somehow that is not being passed correctly. I've never set that up on IIS, so I don't know what all is required to configure it to pass through correctly, but I suspect that IE11 is falling back to HTTPS and not attempting to use Websockets at all, while the rest of the browsers are attempting to use WSS. To confirm this you could try to disable Websockets pass-through entirely, forcing all browsers to fall back to HTTPS, and see if it works. If it does, then you have an issue with the IIS WSS configuration. -Nick
