![iframe refused to connect iframe refused to connect](https://i0.wp.com/i.stack.imgur.com/XcbQm.png)
Solution This issue occurs when one of the following conditions is true: Youre displaying SharePoint Online pages on an external site through an iframe. ClickJacking is where a malicious user loads the site inside of some frame, while using the design of the site to try and get users to pass personal information that can be intercepted or collected. Cross-domain iframe requests to SharePoint Online organizations are blocked. Allowing sites not to load within an iframe by default is a small step to prevent sites from being used for ClickJacking. These settings are implemented by default to implement the best security practices out of the box. These tell browsers that the site should not be loaded within an iframe. Looks like the remote site has decided to block embedding of their site via iframe, doubt theres much you can do other than reach out to the admin and see if. The x-frame-options setting is the original version, while content-security-policy is a newer setting that is not fully supported by all browsers, yet. 1 answer Top answer: I was able to resolve this issue.As I suspected, the x-frame-options error message was a red herring.It ended up being a older SSL/TLS version being. A look at the console shows one error being thrown: Invalid.
![iframe refused to connect iframe refused to connect](https://user-images.githubusercontent.com/3385495/56653924-df146600-669f-11e9-9cd8-f4fab56afeb6.png)
Lessons Learnedįirst, read the developer documentation thuroughly. I’ve created an issue on GitHub and if you have ideas or thoughts, I’d love to hear them in the issue (or the comments of this post).
![iframe refused to connect iframe refused to connect](https://i.pinimg.com/originals/0d/82/4c/0d824c9322b5e1d9f5da416b9eb2dfa9.png)