- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WCF SSL Certificate Errors
Is anyone suddenly receiving certificate errors? A large number of customers are reporting certificate errors when browsing exempted/trusted domains. The SSL logs in the GUI show, "Server certificate blocked".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, can't confirm. We face the same problem on 6.4.6/6.4.7
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
No, I have the problem with v6.4.7 build1911 (GA) firmware.
"SSL/SSH Inspection" profile allowing invalid certificates, it works. Allow invalid certificates, this is probably only possible for a limited number of sites
J.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Per discussion I had with support, if you're on 6.4.x flow-based rules (rather than proxy-based) should work. We unfortunately use proxy-based inspection on our ruleset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here. I had firmware 6.4.6 but upgraded to 6.4.7 build1911 (GA), but the problem is still there ...
I guess we have no other option than to allow invalid certificates, but I don't like it.
Would like to get a recommendation from Fortinet...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I run 7.0.2 and have the same issues. According to Fortinet support, changing the policy inspection mode from proxy to flow is a workaround.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think any Fortigate FW can be immune to this since it's a root cert expiring. We are affected as well for alll the policies on proxy mode on 6.4.6. We changed some to flow mode for a quick fix.
Does anyone know if Fortinet will release an "official" solution soon?
Fortigate : 80E, 80F, 100E, 200F, 300E : 6.4.6
FortiAnalyzer, ForticlientEMS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are on 6.4.7. All policies, web filters are already on flow mode. The only temporary fix is to modify our deep inspection profile to allow expired certificates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I chatted with the support and they told me they will release something via Fortiguard but they have no clue when (I guess in the next few hours since it affects lots of clients). Our Fortinet rep said it affects proxy mode because that expired cert is cached.
Fortigate : 80E, 80F, 100E, 200F, 300E : 6.4.6
FortiAnalyzer, ForticlientEMS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mike_dp wrote:I chatted with the support and they told me they will release something via Fortiguard but they have no clue when (I guess in the next few hours since it affects lots of clients). Our Fortinet rep said it affects proxy mode because that expired cert is cached.
mike_dp wrote:FIX WIN 7: this site's security certificate is not trusted [link]https://youtu.be/0e42USqE-CM[/link]I chatted with the support and they told me they will release something via Fortiguard but they have no clue when (I guess in the next few hours since it affects lots of clients). Our Fortinet rep said it affects proxy mode because that expired cert is cached.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue on 6.4.5 temporarily resolved by following workaround: 1: verify cert bundle is v28 -> diag autoupdate versions -> execute update-now 2: apply DNS blackhole workaround: -> config system dns-database -> edit "1" -> set domain "identrust.com" -> config dns-entry -> edit 1 -> set hostname "apps" -> set ip 127.0.0.1 -> next -> end 3a: flow-mode: -> diag ips share clear cert_verify_cache 3b: proxy-mode: ->:diag test app wad 99
