How can we help?

My Cases

Enabling Cookies and other Browser settings
Last Updated: Dec 26, 2017 03:05PM EST

This article applies to:  Echo360 Students

Echo360 is a web-based application that uses a browser to view content and as such has certain browser requirements. Beyond ensuring you're using a supported browser, there are also some configuration settings you may need to check or change to successfully use Echo360.

If you are using iOS 11 or Safari 11 for Mac and have received a popup box indicating that you must allow cookies/and or cross-site tracking, see Settings for Safari in iOS11 and Safari 11 in MacOS below.

Enabling Cookies in your Browser

Some Echo360 users may not find it necessary to enable cookies in the browser, but many will, especially if they access Echo360 through an LMS (learning management system) or other separate site. Cookies contain some of the current session and authorization information we need to know who you are and to allow you to view content.

The sections below provide basic information for how to enable cookies in each browser type.

Settings for Safari in iOS 11 and Safari 11 in MacOS

Both the MacOS and the iOS versions of Safari used to have 4 levels of cookie settings: Always block, Allow from current website only, Allow from websites I visit, and Always allow.  We have typically recommended you set "Always Allow" to ensure you continue to allow cookies from Echo360 even after you clear your cache and history.

Both Safari for iOS 11 and Safari 11 for Mac has removed the multi/level cookie setting and instead now has two separate toggles/settings for cookies and session/auth information that Echo360 needs, in particular if passing through an LMS. Those are now Block All Cookies and Prevent Cross-Site Tracking as shown in the below figures.

To find these options, go to Settings > Safari then scroll down to the Privacy and Security section of the page.

Both of these settings must be OFF in order to view Echo360 content through Safari on an iOS 11 mobile device.

Safari Settings in iOS11 as described

For Safari 11 on Mac OS, the same options must be turned off. These reside in the Privacy tab of Safari Preferences as shown below.

Safari 11 preferences with Privacy tab shown and options to disable identified

Cookies in Safari 10 on MacOS

The MacOS version of Safari provides 4 levels of cookie settings: Always block, Allow from current website only, Allow from websites I visit, and Always allow.  We have typically recommended you set "Always Allow" to ensure you continue to allow cookies from Echo360 even after you clear your cache and history.

To configure cookie settings:

  1. Open Safari
  2. Click the Safari menu and select Preferences.
  3. Click the Privacy tab
  4. In the Cookies and website data section, enable the Always allow option.
    Safari 10 preferences with privacy tab shown and always allow cookies option identified
  5. Close the Safari Preferences window and refresh or restart your browser.

Cookies in Chrome

Cookies are enabled in Chrome by default. However, in the event they are blocked, you may need to allow them to view Echo360 content. If you are using Chrome across mobile devices (and are signed in with a Google login) the Advanced settings described here are configured on the Primary device and are typically applied across ALL devices.

Chrome retains its cookie settings in the Advanced portion of the Settings page.

Type the word "cookies" in the search box at the top of the Settings page to be directed to the Cookies settings in Chrome. Once there, be sure that Cookies are allowed (allow cookies toggle is turned on) as shown in the below figure.

Chrome settings with cookies allowed as described

Cookies in Internet Explorer

Generally speaking, the "Internet Zone" setting in Internet Explorer Options controls how cookies are handled through the browser, and unless this is set to High and/or Advanced cookie handling has been set, IE will allow cookies from sites as needed.

However, if you do need to explicitly set or change your Internet Explorer cookie handling, click the Settings icon in the top right corner of the browser, then click Internet Options from the menu.

In the dialog box that appears, click the Privacy tab, and set the Internet Zone to Low. This ensures you can view Echo360 content inside of a Frame (such as your university portal or an LMS window).

Then click the Advanced button. This is shown in the below figure. Enable the Advanced cookie handling checkbox, then set Accept all for cookies.

Internet explorer options with Privacy tab, Advanced button, and Advanced options shown as described

Configuring Browsers for LIVE streaming

Live streams are tested on and supported for viewing using all of the above-listed browsers, as long as your installed version of Adobe Flash is the most recent. (Adobe will probably let you know if it needs to be updated...they're good like that.)

Note that our testing indicates that Live streaming from a CCAP appliance works most reliably when viewed through Google Chrome.

Provide browser permissions to play Flash content: Chrome and Safari do not natively allow websites to play Adobe Flash content. While you may receive a message that your Flash Player is out of date, it is more likely that you need to update your browser permissions to either always allow Flash to play, or set an exception for the Echo360 URL to allow Flash. If you choose to set an exception, be sure to list your region's URL specifically (,,, or
See for Chrome instructions, and/or for Safari instructions.

If viewing the Live stream on a mobile device, Echo360 automatically buffers 40 seconds of the stream to ensure smooth playback. This means you may experience a delay in the start of the stream, and that your view will lag anywhere from 30 seconds to a minute behind the real-time action.

Despite using Flash, iOS allows for Live stream viewing. How? iOS uses HLS instead of Flash for live streaming. (HLS stands for HTTP Live Streaming Protocol, in case you were interested.)

Unfortunately Android devices CANNOT be used to view Live streams. We hope to address this in the reasonably near future.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found