Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Embedded Instagram Posts no longer show on forums.

  • 2 àwọn èsì
  • 1 ní ìṣòro yìí
  • 6 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ cor-el

more options

Hello,

I have never had any previous problems with Firefox until today, when embedded Instagram posts were no longer visible on forum websites. The posts are now replaced with the following:

"Firefox Can’t Open This Page

To protect your security, www.instagram.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.

Learn more…

Report errors like this to help Mozilla identify and block malicious sites"

Opening the page in a new window does not work and I am using the very latest version of Firefox.

Does anyone, at all, have any resolution to this problem? A great many thanks in advance.

Thank you

Hello, I have never had any previous problems with Firefox until today, when embedded Instagram posts were no longer visible on forum websites. The posts are now replaced with the following: "Firefox Can’t Open This Page To protect your security, www.instagram.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window. Learn more… Report errors like this to help Mozilla identify and block malicious sites" Opening the page in a new window does not work and I am using the very latest version of Firefox. Does anyone, at all, have any resolution to this problem? A great many thanks in advance. Thank you

All Replies (2)

more options

Please go to ≡ -> Privacy and Security and check if you have the Strict or Standard tracking protection.

more options

It is possible that Instagram starting adding a X-FRAME-OPTIONS header in the HTTP response headers or prohibits this via CSP rules.

You can check this in Network Monitor.

If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.