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".

Tìm hiểu thêm

I keep getting unsecured web site warnings that won't let me access sites.

  • 3 trả lời
  • 34 gặp vấn đề này
  • 5 lượt xem
  • Trả lời mới nhất được viết bởi Xircal

more options

Every time I try to access my bank's website and log in I get a warning about entering an unsecured website. Then I'm instructed to add exception which I click on, then I'm told to add certificate.When I click on add certificate it goes back to the entering unsecured site warning. I think the problem is in the security settings in Firefox.

Every time I try to access my bank's website and log in I get a warning about entering an unsecured website. Then I'm instructed to add exception which I click on, then I'm told to add certificate.When I click on add certificate it goes back to the entering unsecured site warning. I think the problem is in the security settings in Firefox.

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

more options

I have the same problem and have been looking for a solution forever! Its not just Firefox though its our computers security settings because I get the same thing when trying to use internet explorer. If any one knows how to fix this please post a solution!

more options

I just found out the problem. My date on my computer had changed itself to the year 2004. Since my computer thought it was 2004 all the 2011 certificates wouldn't work! So change your date to the right year and fixed!

more options

It would be wise to phone your bank to ask them if they're aware of the problem.

Not so long ago, thieves managed to steal a number of SSL certificates used to authenticate secure sites. These can be used to create a banking site for example. These certificates were blacklisted in Firefox 3.6.17 and above so that they'll be rejected if you inadvertently surf to a fake site. You can read about it on the Comodo blog @ http://blogs.comodo.com/it-security/data-security/the-recent-ra-compromise/

I don't know if that's the case here, but as I mentioned before, your first port of call should be to your bank's customer service department in order to determine whether they're aware of the problem or not.


If this answers your question, please click the Solved it button next to this post after you log in into the forum. This will help others searching for a solution to the same thing.

Thanks.