Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Secure Connection fail when using https://www.website.com; Error code: sec_error_bad_signature)

  • 2 trả lời
  • 19 gặp vấn đề này
  • 76 lượt xem
  • Trả lời mới nhất được viết bởi cor-el

more options

Why, when I use Internet explorer, I can utilize https, but unable to use it in mozilla?

Why, when I use Internet explorer, I can utilize https, but unable to use it in mozilla?

Tất cả các câu trả lời (2)

more options

Click the site identity button - More Information - View Certificate https://support.mozilla.org/en-US/kb/how-do-i-tell-if-my-connection-is-secure

Look for 'Issued By' and post that information.

Note that some anti-virus/firewall software and programs like Sendori, FiddlerRoot, or BrowserProtect can intercept your secure connections and send their own certificate instead of the website's certificate.

more options

Clear the cache and cookies only from websites that cause problems.

"Clear the Cache":

  • Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"

"Remove Cookies" from sites causing problems:

  • Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

Check the date and time and time zone in the clock on your computer: (double) click the clock icon on the Windows Taskbar.

Try to rename the cert8.db file in the Firefox profile folder to cert8.db.old or delete the cert8.db file to remove intermediate certificates that Firefox has stored.

If that helped to solve the problem then you can remove the renamed cert8.db.old file. Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previous intermediate certificates. Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.

If that didn't help then remove or rename secmod.db (secmod.db.old) as well.