当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Messsge - "This connection is Untrusted. You have asked Firefox to connect securely to secure.listenernetwork.com but can't confirm that your connection is secure...." What do I need to do to fix this problem?

  • 2 件の返信
  • 18 人がこの問題に困っています
  • 5 回表示
  • 最後の返信者: myaand

more options

A couple days ago I updated Firefox. Today when I try to login to my sports sites where there is a trivia points earning system I get the following pop up box and can't log in - "This connection is Untrusted. You have asked Firefox to connect securely to secure.listenernetwork.com but can't confirm that your connection is secure...." I can't even get to the lower portion of the pop up to see what the "Technical Details" and lower portion says. What do I need to do to fix this problem?

A couple days ago I updated Firefox. Today when I try to login to my sports sites where there is a trivia points earning system I get the following pop up box and can't log in - "This connection is Untrusted. You have asked Firefox to connect securely to secure.listenernetwork.com but can't confirm that your connection is secure...." I can't even get to the lower portion of the pop up to see what the "Technical Details" and lower portion says. What do I need to do to fix this problem?

すべての返信 (2)

more options

Are you using extensions that can force a sure HTTPS connection?

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).

more options

Thanks for your suggestion to correct my issue. However, the issue seems to have cleared up. It's possible it was in fact a problem with the Web Site itself. I will keep your possible solution in case the issue repeats itself.