You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2016/08/24 02:30:20 UTC
[jira] [Updated] (GUACAMOLE-85) Connection fails with Microsoft
Edge
[ https://issues.apache.org/jira/browse/GUACAMOLE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Jumper updated GUACAMOLE-85:
------------------------------------
Component/s: (was: guacamole-auth-noauth)
guacamole-common-js
guacamole
> 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
> Environment: The guac components reside on centos with a standard installation in a no-auth setup. Clients accessing the web portal via Microsoft Edge Version 25. (have to get the specifics) receive the errors listed below. 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.
> Reporter: Brian E Henry
>
> 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)