iPad issue loading videos in html5 and SSL

Jun 06, 2013

Dan Marsden
By Dan Marsden

I have a client who has some SCORM 1.2 packages built with storyline that contain videos that usually work fine on the iPad using HTML5

the content works fine on a site using plain http but fails on the same site when https is switched on - apparently it used to work on older iOS versions (currently failing on iOS 6.1.3) but I haven't been able to confirm that.

The content views fine in both http/https using FF/Chrome - tested and reproduced in Moodle 2.2 and 2.5

Has anyone seen this before or have any ideas on the cause?

11 Replies
Christine Hendrickson
over 10 years ago06/06/13 at 9:04 am (UTC)

Hi Dan,

A https website, in general, shouldn't conflict with running your course on the iPad. Is your https site also password-protected? If so, that may be causing an issue.

You may also want to make sure you're publishing with the most recent version of Storyline. To find this information, click on "Help" and "About Articulate Storyline".

If you're not running version 3 (1305.2012), please download and install the update using the link below:

 Articulate - Storyline Update 3

Once you've finished installing the update, please republish and test your course on the iPad. If the problem continues after installing the update, or if you already have Update 3 installed, please let me know.

If the issue continues, can you tell me exactly what steps you're taking to access the course and what happens when you view it? Does it load at all, or are the videos just missing?

Thanks!

Dan Marsden
over 10 years ago06/06/13 at 7:29 pm (UTC)

Thanks Christine,

yeah - I know it shouldn't interfere but it seems to be doing something wacky at the moment... the site uses standard authentication provided by Moodle so is "password protected" - but no different from normal - and it works fine when just using http

I'm told they are already using update 3

Here's a screenshot of what happens to an embedded video when SSL is used for the site: (fulltime https:// - http redirects to https)

My earlier testing didn't show an image on first load like it does in the screenshot above but a black screen with the broken play image in the middle.

How does the package detect if html5/flash should be used?

Christine Hendrickson
over 10 years ago06/07/13 at 7:50 am (UTC)

Hi Dan,

I'd almost prefer to see the black image/placeholder you first saw - I haven't seen that image and error combination before. 

My first thought would be the MIME type for the server, but I'm not sure if that would apply here or not. 

Just in case:

Maybe that'll do the trick. If the SSL is working fine in SCORM Cloud, it comes down to the Moodle server, honestly. 

If all else fails, we'd be happy to take a look at the project and see what's going on. You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks very much, Dan!

Christine

Dan Marsden
over 10 years ago06/09/13 at 8:09 pm (UTC)

Thanks for the help Christine -

We're going to switch to run SSL for login-only as this particular site doesn't need full-time SSL - MIME types should be set correctly but it's worth checking to make sure anyway.

If anyone else finds this post and is having similar issues drop me an e-mail, I'd be interested to hear if it's something specific to us.

rosy colelli
over 10 years ago08/06/13 at 2:27 am (UTC)

Dan Marsden said:

Thanks for the help Christine -

We're going to switch to run SSL for login-only as this particular site doesn't need full-time SSL - MIME types should be set correctly but it's worth checking to make sure anyway.

If anyone else finds this post and is having similar issues drop me an e-mail, I'd be interested to hear if it's something specific to us.

Dan Marsden
over 10 years ago08/06/13 at 1:59 pm (UTC)

It was a combination of issues for us - switching off full-time SSL got us half way there but then we found an issue with mem_cache interfering with the files - (mem_cache is an Apache module, part of the web server software) - after switching off full-time ssl, disabling mem_cache also appeared to resolve it for us.

let us know how you go!

This discussion is closed. You can start a new discussion or contact Articulate Support.