you could also try hitting the advanced button and then continue, just to see where it takes you, check to see if it looks like facebook or if it's a fake site for password phising or something. After getting into the site, you could check to see if the IP address matches with what it should be as well, Use wireshark or you might be able to find it under Sources or network tab in the DevTools page on chrome (right click anywhere on page and select inspect).
There is nothing from any of the 7 other machines on the network indicating there is anything new. There are no portals or additional logins to be had. The issue being only facebook (which I can ping) and that I get the same type of error on multiple browsers. That is the weird part. And advanced does not go to the standard "continue on to site unsecure" ability.
Certain sites are giving us a ERR_SSL_PROTOCOL_ERROR only in Google Chrome. I have tried all the usual troubleshooting for this error, but the only thing that fixes it is restarting the fortigate. Two sites (facebook.com and login.renweb.com) both use TLS 1.3, but we can get to facebook without a problem and we cannot get to the other site. After rebooting the device, it works for several days and then starts behaving poorly again.
This has been an issue for quite sometime and I've put it on the back burner. From time-to-time and only on a very few machines (dell optiplex 790's etc...) I will encounter security issues when trying to see our library website, facebook, and other common legit sites. For example, I have several spare machines that I can deploy into the building when necessary. Recently, I decided to get one of them and install Windows 10 with the media installation download from Microsoft. The computer had Windows 8.1 at the time. I noticed certificate errors almost everywhere I went. I decided to go ahead and bring it up to Windows 10, which is now complete. It's bare bones with 10 and Edge installed and that's about it. I hopped onto the network and noticed the same thing right away....certificate errors. The clock and global settings are correct, etc...
This isn't an issue with any of the other 18 computers on the same network. I noticed the error message reporting..."Fortinet" wasn't installed properly on your computer or the network: NET::ERR_CERT_AUTHORITY_INVALID". That gave me an idea. I have a linksys router configured to pass the traffic in and out of the network in case the Fortigate fails, etc... So, fired up the router and put the outside on the WAN and the inside on the LAN1 port - gave it a minute and then went to the computer that had the difficulty and there were no longer any certificate errors at all. I reversed the above and put the cables back into the Fortigate and again had the certificate problems reappear. Where could I look in the settings on the Fortigate to investigate where the cert errors are originating? Thanks!!
Have you tried accepting the certificate errors to navigate to the page? Usually these errors come up when the FortiGate is blocking content for one reason or another, and that reason is usually explained on the page it is trying to present.
In these situations the FortiGate is essentially acting as a MiTM attack, presenting a different certificate (its own) than the browser is expecting (i.e. Facebook, your library, etc). So it's not so much a matter of fixing the certificate error as fixing whatever is causing the block to happen.
Under Policy & Objects --> IPv4 Policy ---> There were several of my machines listed here from the network. One of them was the one in question mentioned in my original post. I deleted those entries and then tested the machine. The certificate errors no longer occur.
Chrome relies on your computer's time and date to make sure that the SSL certificate is authentic and current. If your time is wrong, it can generate a privacy error. For the best results, make sure your computer is configured to automatically set the time from the internet.
I recently installed Sophos XG firewall on my home system. When I enable a web policy in the predefined default network rule, I get invalid certificate errors when browseing certain websites, for example Facebook. FB will not allow any access. I have gone into System-->Certificates and there is a certificate called Appliancecertificate. When I click the manage icon, it goes and gets a new copy without error. However that does not fix the problem.
I recently switched to a new laptop running Windows 7. For some reason I am constantly getting certificate errors when hitting sites where I really shouldn't be getting them - twitter, picasa, google analytics (but gmail works), my bank, etc.
If you have a DigiCert certificate and you receive this error, troubleshoot the problem using the sections below. You do not need to install anything on client devices/applications for a DigiCert SSL Certificate to work properly. The first step is to use our SSL Certificate tester to find the cause of error.
One possible cause of this error is that a self-signed certificate is installed on the server. Self-signed certificates aren't trusted by browsers because they are generated by your server, not by a CA. You can tell if a certificate is self-signed if a CA is not listed in the issuer field in our SSL Certificate tester.
The most common cause of a "certificate not trusted" error is that the certificate installation was not properly completed on the server (or servers) hosting the site. Use our SSL Certificate tester to check for this issue. In the tester, an incomplete installation shows one certificate file and a broken red chain.
If you receive an error using our SSL Certificate tester, you are using a Windows server, and your certificate's issuer is listed as "DigiCert High Assurance EV CA-3", please see this article for instructions on troubleshooting a SSL installation error.
Your browser verifies a site's security certificate to confirm the site will protect your privacy while visiting it. If a certificate is not up to standard, this means your personal data might not be encrypted and therefore susceptible to online threats. In short, a "your connection is not private" error means just that: Your connection is not private, and the error isn't something to ignore.
In late September, though, Let's Encrypt saw its root certificate expire. Those relying on older devices to connect to the Internet, then, might have seen an increase in the number of "Your connection is not private" errors as they searched the web.
Before entering a website, your browser checks digital certificates of that website to ensure they're meeting requirements and will safeguard your private information, such as contact information, passwords, and payment methods, usually via encryption. Most often, the "your connection is not private" error lies in a site's Secure Sockets Layer (SSL) certificate, which is required for sites running over HTTPS (connection security). If your browser can't verify an SSL certificate, it stops you from visiting the site by giving you the "your connection is not private" error message.
It comes from a certificate issue emitted by DigiCert, It is the DigiCert Global Root G1A.Yet this certificate does not exist, in DigiCert database. And worse, on their dignostic tool, the websites use the DigiCert Global CA G2I could not bypass the certificate acceptance because of HSTS protocol.I looked at the clock, no problem. I used chrome, it worked.
While it does not always mean a website is unsafe to browse, it should not be ignored. A secure internet connection is critical to protecting yourself online. Many nefarious websites are dangerous to visit, and this SSL certificate error will protect you from walking into them unaware.
As we discussed in this post, this error can be caused by several different things. The most likely culprits are incorrect cache settings, old or expired certificates, and incorrect protocol or system settings. By clearing your cache, checking your SSL certificate, and updating your protocol and privacy setting, you should be able to resolve this issue in no time.
When a website tries to establish a secure (HTTPS) connection with the PC. The Firefox browser checks the site certificate to make sure the connection is safe and secure. Sometimes, Firefox is not able to make a secure connection and shows a warning like Secure Connection Failed. The page also displays details of an error.
so when I type in the external domain name into a browser of a non-local computer, my test website from that server loads fine over HTTPS, no certificate error whatsoever.
but when I first connect to my local network using SSTP VPN (VPN host name is the same as the external domain name that points to my server's public IP address), and then once i'm connected, I try to use the local domain name of my server in the browser, i get this certificate error.
Often, when a user receives a security certificate warning, they simply select Continue without understanding why the error is occurring. To avoid encouraging this habit, you can prevent the warning from appearing in the first place.
But that didn't helped on any client computer except the Qlik Sense server itself. So when I logon to the Qlik Sense server through remote desktop, open the browser (Chrome) and click on the On Demand button it works, but doing the same on any other computer/server after accepting the Qlik Nprinting web console certificate I still get the same error message.
 3ae0bdd00e