Kevin,

This is a known issue right now. The current workaround is to manually navigate to the http version of the page instead of https, then it should work as expected. Let me know if this works for you or not.

[...] [[...]]

Thanks, Colin Login to read more.