Adobe Connect User Community
Menu

#1 2015-05-27 15:40:16

azpeter2009

GOOGLE CHROME 43 PROBLEMS

Google Chrome 43.xxxx (released 5/19/15) is NOT connecting reliably with Adobe Connect 9.3 (at least our on-premise system). Users without the Adobe Connect Add-In installed may get stalled or stuck on the "Connecting..." screen.

Users running the Connection Test get the "ERROR: FMS Server did not return correctly!"

Suggested work-arounds:
--Use a different browser to connect to the room.  Internet Explorer (WIN), Firefox (WIN & Mac OS), or Safari (Mac OS) should connect, even without the Add-In.
--Use a different browser to run the connection test.  If it passes the connection test, it should get to the point to Install the Add-In.  Then it should be possible to connect to the room, even in Google Chrome.
--To FORCE the installation of the Add-In, add the text "?lightning=true" to the end of the room URL, either in the browser address bar (even Chrome), or in the link to click, provided to users.
Example:  http://my.adobe.com/MyRoomURL?lightning=true
--If you have a way to downgrade back to Google Chrome 42.xxxx, try that, or select another browser as the default browser until there is an updated Google Chrome confirmed as working with Adobe Connect.

This seems to be a Google Chrome issue, since the problem appeared with the release of Chrome 43.xxxx, on Windows and Mac OS.
ADDITIONAL INFORMATION (5/28/15):  Troubleshooting has revealed that Google Chrome v. 43 is NOT allowing MIXED CONTENT (from secure (https:) and non-secure (http:) servers), whereas Chrome v. 42 DID allow MIXED CONTENT.  We are researching certificates and security settings, but in the meantime, we are suggesting users use Firefox, unless they already have the Add-In installed)

I have posted this information for our end-users at http://links.asu.edu/ACchrome.

Last edited by azpeter2009 (2015-05-28 19:35:12)

Offline

#2 2015-08-28 13:58:05

azpeter2009

Re: GOOGLE CHROME 43 PROBLEMS

We eventually identified this as caused by the firewall/load balancer/whatever using TLS 1.0.  When reconfigured to TLS 1.2, it is working, for now. 
It was the Connection Info on the Chrome padlock icon that was marked with a YELLOW TRIANGLE on the -QA server (which WAS WORKING), compared to the Padlock with the RED X on the Production server (which WAS NOT WORKING), which lead me to the solution.
I think there is still an upgrade in our future when SHA1 is no longer supported.

Offline

Board footer