We have run into an issue where all of our modules that load iframes using the HTML module type are throwing errors when viewed in Microsoft Edge in Windows 10. No matter what URL we load, they display "Hmmm...can't reach this page". Has anyone else experienced this issue when trying to use iframes?
I think we may have narrowed it down to our Windows 10 image(s) that we deploy to machines on campus, because it appears to be working fine on people's personal computers using Windows 10 at home. I will definitely update with more info as we continue to work on the issue.
Well, we have tracked down the issue, but we still do not have a solution. Here is a basic summary from stack overload:
"It turns out Edge fails to load a private/local secured SSL page (iframe) when in-conjunction of loading a public secured page. Both sites are secured using public SSL certificates to prevent mixed content issues. The issue is that Edge security detects that the iframe site is located on the users local network (private/domain network) and prevents the page from loading in an iframe."
Our Blackboard is externally hosted. Much of the content that we are pulling into iframes comes from sub-domains of monroecc.edu (our domain). Users who are accessing Blackboard via machines joined to our domain (offices, labs, classrooms) encounter this error, because the iframe content is considered "local" on our domain, while Blackboard is considered external. Users accessing Blackboard from personal machines or off campus do not encounter the issue.
Right now we are still trying to come up with a solution/work-around.
Here's a link to the stack overflow thread that led us in the right direction finally: SEC7117 Error when trying to load a javascript file in MS Edge - Stack Overflow
RESOLVED: We were able to resolve the issue by adding the externally hosted URL for our Blackboard instance as a "Trusted Site" in our domain group policies.
Help
Privacy
Behind the Blackboard
Blackboard.com
Hi Jamie,
We have seen this when we use the embedd code from our Panopto server. It displays as you have noted - "Can't reach this page". When viewed from Chrome, it works fine. I have asked our local IT team to look into it, but they have not returned any suggestions. Let me know what you find out.