[
https://issues.apache.org/jira/browse/GUACAMOLE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447295#comment-15447295
]
Michael Jumper commented on GUACAMOLE-85:
-----------------------------------------
{quote}
Tomcat 7
{quote}
But which exact version of Tomcat 7? WebSocket cannot be used with versions
older than 7.0.37, which would lead to that initial 404. This is not the cause
of your trouble, but something to keep in mind if you want WebSocket to work.
Reading up on the error code "0x2EFD", this error is returned by Windows' HTTP
client when it cannot establish a connection for any reason. [Microsoft's docs
for that
error|https://msdn.microsoft.com/en-us/library/windows/desktop/aa383770(v=vs.85).aspx]
are equally non-specific:
{quote}
...
h4. ERROR_WINHTTP_CANNOT_CONNECT
12029
Returned if connection to the server failed.
...
{quote}
In the context of Edge, I see this reported widely for:
# Access to private networks being blocked
# Just about any network failure
If other browsers work within the user's network, that suggests the issue is
not network-specific. The possible causes are too numerous to attempt to
troubleshoot here, but I can at least confirm that this isn't a bug in
Guacamole. I have retested everything against Edge, and all is fine.
My best suggestion for the sake of getting things moving forward on your end is
to check Edge's settings, specifically with respect to "Enhanced Protected
Mode":
http://stackoverflow.com/questions/32581503/microsoft-edge-blocked-cross-domain-requests-sent-to-ips-in-same-private-network
Given that you mention the NoAuth extension, and given the nature of this
error, I suspect that you may be serving Guacamole from within an iframe, and
that the site containing that iframe is not served from the same domain as the
Guacamole server. If not, then great - ignore this paragraph. Otherwise, beware
that this is *highly* not recommended due to:
# The difficulty of handling cross-origin / CORS (it is much easier to proxy
everything to a single domain and not worry)
# Issues with the behavior of keyboard focus with respect to iframes.
As you also mentioned that users are coming in on port 443, but might be being
redirected to port 8080, I am additionally concerned with respect to security
and/or cross-origin. Users should not be being redirected to different port
just for Guacamole traffic. If your main web application is being encrypted and
served over 443, then the same should be done for Guacamole. This is normally
achieved using a reverse proxy like Apache or Nginx:
http://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html
> 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)
