為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

I cannot sign-in to my Barnes and Nobles account. If I disaple protection temporarily I still cannot sign-in. I get not information as to why the site is bloc

more options

I cannot sign-in to my Barnes and Nobles account. Security indicates it is blocking 'MIXED CONTENT'. If I temporarily disable mixed content, I still cannot sign-in. I have cleared my cache to no avail. Security also says tracking protection has blocked the site. I temporarily disable tracking protection, still cannot sign-in. This is not the first time this has happened. I have been forced to use Chrome to sign-in on these sites. How do I determine why these sites are being blocked? If Firefox has a legitimate reason for blocking these sites, that would be okay as long as I know why and how to correct the problem.

I cannot sign-in to my Barnes and Nobles account. Security indicates it is blocking 'MIXED CONTENT'. If I temporarily disable mixed content, I still cannot sign-in. I have cleared my cache to no avail. Security also says tracking protection has blocked the site. I temporarily disable tracking protection, still cannot sign-in. This is not the first time this has happened. I have been forced to use Chrome to sign-in on these sites. How do I determine why these sites are being blocked? If Firefox has a legitimate reason for blocking these sites, that would be okay as long as I know why and how to correct the problem.

被選擇的解決方法

Did you check FF security settings to except Barnes and Noble as trust site?

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

選擇的解決方法

Did you check FF security settings to except Barnes and Noble as trust site?

more options

Since posting this problem, I have now been able to sign-in to my Barnes and Nobles account. I don't know why. I have re-enabled all protections and I can still sign-in. I don't know what changed. Since the problem no longer exist on this website, I will mark the problem as solved but really nothing changed.