Sorry for replying to an old thread, but I finally resolved the issue I was
having and thought it might help someone if they ever run into it.
Ahead of trying to get 1.2.0 going on my test server (debian) I wiped out
my tomcat8 configuration and started over with the default tomcat9
configuration
See log below -- from Chrome 73 error console upon reloading a session that
started to connect then threw the connection error being discussed. This is
on 1.0.0 with websockets.
On 1.0.0 with Slimjet (Chrome 72) I only see the "angular.js:12845 GET
On Thu, Apr 4, 2019 at 19:07 Mike Jumper wrote:
> Just retested with Chrome OS 73.0.3683.88 - still working absolutely fine
> for me.
>
> - Mike
>
Same, here. Multiple revisions of the code from 0.9.14 through git master
and some pull requests, and it works fine with the latest chrome.
-Nick
Make sure that your Chrome is not installed with adblockers and if the error
keeps occurring, go in to debug mode with inspect elements and list the
errors. I do know Chrome will complain if the certificate chain is not
complete. You will get https (SSL) but if the chain key is not created
Just retested with Chrome OS 73.0.3683.88 - still working absolutely fine
for me.
- Mike
On Thu, Apr 4, 2019 at 3:19 PM Hankins, Jonathan <
jhank...@homewood.k12.al.us> wrote:
> This has started happening for me recently after a Chrome upgrade. I am
> seeing this on 1.0.0, with websockets
This has started happening for me recently after a Chrome upgrade. I am
seeing this on 1.0.0, with websockets configured. *NOT* seeing it on 0.9.14
without websockets. Has been working fine on 1.0.0 w/ websockets previously.
Experiencing error with these browser versions:
(Linux)
Google Chrome
On Mon, Apr 1, 2019 at 1:33 PM elvelux wrote:
> I have recently discovered that the error only occurs connecting by https,
> no
> by http.
>
>
I use Guacamole 1.0.0 with Chrome and HTTPS routinely with no issues.
-Nick
Thanks for the reply. Unfortunately we dont have reverse proxy implemented.
--
Sent from:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
I had an odd problem where Windows and Linux desktop browsers would work
fine but the 'Blackberry Access' browser wouldn't (not sure what browser
that is 'under the hood').
In the end it was because of a misconfiguration on the reverse proxy we
have in front of the Guacamole server - the
On Mon, Apr 1, 2019, 03:57 elvelux wrote:
> Hi,
> I have troubles with guacamole 1.0 and Chrome. Using firefox or explorer
> the
> connection going well but with chrome, the message "Conection error"
> inmediatically appears.
>
What error?
"Connection error" is only the title of the dialog
Hi,
I have troubles with guacamole 1.0 and Chrome. Using firefox or explorer the
connection going well but with chrome, the message "Conection error"
inmediatically appears.
I have guacd in debig mode. In logs i dont see any error. Do you know if
there any incompatibility?
thank you in advance.
11 matches
Mail list logo
