Certain network setups will cause errors in recent browsers when trying to embed links to media.
The root cause is the Moodle system being visible on both internal and external networks. When seen as internal (e.g. directly connected on campus or via VPN) new security controls in Chrome 142 (and other browsers to follow) will interpret this as an IFrame in the web browser trying to access items on the users home network and block it as a security measure.
The error states: "The connection is blocked because it was initiated by a public page to connect to devices or servers on your private network. Reload this page to allow the connection."
Full details of the underlying issue are available on this Moodle tracker ticket which implements a fix for the core LTI 1.3 support, which hit the same issue and added an attribute the iframe to trigger a permission prompt when necessary:
https://moodle.atlassian.net/browse/MDL-87258
Certain network setups will cause errors in recent browsers when trying to embed links to media.
The root cause is the Moodle system being visible on both internal and external networks. When seen as internal (e.g. directly connected on campus or via VPN) new security controls in Chrome 142 (and other browsers to follow) will interpret this as an IFrame in the web browser trying to access items on the users home network and block it as a security measure.
The error states: "The connection is blocked because it was initiated by a public page to connect to devices or servers on your private network. Reload this page to allow the connection."
Full details of the underlying issue are available on this Moodle tracker ticket which implements a fix for the core LTI 1.3 support, which hit the same issue and added an attribute the iframe to trigger a permission prompt when necessary:
https://moodle.atlassian.net/browse/MDL-87258