When I go to the following website, CRON-O-Meter Track nutrition count calories , I get the following message. As of a few months ago, I had visited this website without any issues. I've written to Cronometer and they say that they've not received any similar complaints. I've done a factory reset of the Revue, but that didn't resolve the issue. No other website that I visit has this issue. Time and date is set up correctly. How does one go about finding and deleting a non-valid or corrupted security certificate? And then reinstalling the updated certificate? The owner of this website said that the "entity" that he uses is godaddy(?). Does anyone else with a Logitech Revue get this same message when they visit Cronometer? --------- The site's security certificate is not trusted! You attempted to reach cronometer.com, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Google Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site. Help me understand When you connect to a secure website, the server hosting that site presents your browser with something called a "certificate" to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network). In this case, the certificate has not been verified by a third party that your computer trusts. Anyone can create a certificate claiming to be whatever website they choose, which is why it must be verified by a trusted third party. Without that verification, the identity information in the certificate is meaningless. It is therefore not possible to verify that you are communicating with cronometer.com instead of an attacker who generated his own certificate claiming to be cronometer.com. You should not proceed past this point. If, however, you work in an organization that generates its own certificates, and you are trying to connect to an internal website of that organization using such a certificate, you may be able to solve this problem securely. You can import your organization's root certificate as a "root certificate", and then certificates issued or verified by your organization will be trusted and you will not see this error next time you try to connect to an internal website. Contact your organization's help staff for assistance in adding a new root certificate to your computer.