[
https://issues.apache.org/jira/browse/GUACAMOLE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434096#comment-15434096
]
Michael Jumper commented on GUACAMOLE-85:
-----------------------------------------
The finally-fatal error here is the one regarding XMLHttpRequest. Guacamole is
retrying via HTTP once WebSocket has failed, but once both WebSocket and HTTP
have failed, Guacamole gives up and displays that error.
I agree that both of those attempts failing does suggest a network problem,
though the initial 404 for WebSocket may be due simply to your version of
Tomcat not having WebSocket support.
Can you please confirm:
# What version of Tomcat is serving Guacamole?
# Is there anything on your network which might be interfering with (or
rewriting) the HTTP response from Guacamole?
# Is Guacamole running on the same local/private network as Edge in this case?
IE has a flag enabled by default which forces quirks mode for absolutely all
pages served from the local network, which naturally breaks Guacamole. I'm not
sure if Edge has the same anti-feature, but it may be worth a look.
> Connection fails with Microsoft Edge
> ------------------------------------
>
> Key: GUACAMOLE-85
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-85
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-common-js
> Affects Versions: 0.9.9
> Reporter: Brian E Henry
> Priority: Critical
>
> Clients accessing the web portal via Microsoft Edge Version 25 (have to get
> the specifics) receive the errors listed below:
> {quote}
> An Internal error has occurred within the Guacamole server, and the
> connection has been terminated. If the problem persists, please notify your
> system administrator, or check your system logs.
> {quote}
> Developer Tools reports:
> {quote}
> WebSocket Error: Incorrect HTTP response. Status code 404, Not Found
> XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due
> to error 00002efd
> {quote}
> The guac components reside on CentOS with a standard installation in a
> no-auth setup. The guac interface does work on Mozilla. Referencing the
> internet there could be two possible resolutions. One that the port coming
> in on 443 but getting redirected to 8080, it does not like or the private
> network is not known.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
