Published Course does not work in Chrome

My course ran fine in IE but not in Chrome (see attachment) until I changed the security options in Chrome. I just updated to the latest installation (Update 12: 1705 520) for Storyline 2.   After updating my course and posting again online, it still does not run in Chrome (tested on another's computer and my iPhone since my security is updated).   I can't imagine telling all of our users that they have to update their security options in Chrome... or use IE. Any one have any thoughts? 

17 Replies
Leslie McKerchie

Hi Dee! 

I don't think you are going in circles, but I do see where the conversation could be confusing.

Here's what I found in my testing:

1. Your link on your temporary server ONLY works in Flash - it does not work in any browser that does not utilize Flash first - failed for me in Firefox, Chrome, and Safari.

2. Publishing your file to Tempshare works as expected for me in all environments - looks like this worked for you as well.

3. If you are publishing for the web, you should not need to add any locations that the local article shared. Have you tested on your actual web server yet?

I'm not clear on if you have published for Tempshare for some comparison testing yourself.

We typically see the issue you are seeing when the user is viewing the HTML5 content in an unsupported browser, but this does not seem to be the case for you.

If the content works when you publish and upload to Tempshare, you may need to look into the specs of your web server to see why this is not working.

I have made a note in your case that I was responding to you here and it looks like Eloisa did reach out for clarification from a Senior Support Engineer, but we can certainly escalate your case if needed.

Dee Thomas

Thank you for your testing.  I guess my question is "why" is it that my link on my temporary server ONLY works in Flash - it does not work in any browser that does not utilize Flash first - failed for me in Firefox, Chrome, and Safari.  How can I get it to work on my server?  Is the common denominator "My Server" (that's what I'm hearing). If so, do you have any ideas of what I should check on my server? 

Leslie McKerchie

'Why' is the toughest Dee.

It's precisely why I was asking if you are able to replicate in any other environment. Your actual server or Tempshare (then you could compare perhaps).

Update Eloisa on your testing via your case and then, as I mentioned before, we can escalate to see if your Senior support can dig a bit deeper.

The inability to replicate via Tempshare on my end, does seem to indicate something with the server, but that is not something I'm savvy with.

Dee Thomas

I just received Eloisa's reply only to be told what I already knew and started the conversation with.  The course does not work until the security options are changed in Chrome - which would have to be set on each individual's computer running the course.  As I said when I started the post.  "I can't imagine telling all of our users that they have to update their security options in Chrome... or use IE."   13 days later I'm still at square 1.  Attempts to help is not lost on me and is much appreciated... just not the result I was hoping for.

Ashley Terwilliger-Pollard

Hi Dee, 

I'm sorry for the frustration and confusion around this issue. I took a look at your case history and the help Leslie has provided here to try and clear a few things up. 

  • The behavior with security settings in Chrome or other browsers appeared limited to your server, since Tempshare worked as expected.
  • The settings you'd need to change within your server are not something our team can do or provide direct help on.
  • Eloisa's last suggestion to add your server as a trusted site would have to be done on each machine who ran into the security settings. Perhaps your IT team has a way to deploy this to a number of computers?
  • If the course is currently hosted on a test server, is that different than where users will be accessing the course once live? If so, I'd test it there - as it may only be the test server causing the security issues. 

Again, I'm sorry for the lack of clarity here and any added frustration it caused. If there is anything else I can help with, please let me know.