"No records found" at the SSL/TLS Inspection Rules Tab after adding multiple Rules.

Just to be sure: If you use other browser, delete caches etc. will it resolve the problem? 

I've already cleaned the cache multiple times and just tried to open the TLS Inspection tab with a brand-new Firefox installation, but the problem persists.

I'm going to reboot the firewall later to see if that fixes this issue.

Thanks!

Oddly enough, this should not be the case. Can you give us the Access ID? Do you have a official License and can put a Feedback? 

I've just submitted a feedback with more explanation and with an attached picture.

I will send you my Access ID through a private message soon.

Is there any log file where I can look at it?

Just to understand why this is happening.

I was wrong, even after creating a new TLS Inspection Rule, it won't show it on the Web UI and doesn't work as expected.

Looking at the SSL/TLS Inspection Logs It only shows connections to sophos.com as It's allowed through the hidden rule #0.

Nothing else shows in the Logs besides this.

You could do a csc debug (csc custom debug) and check the csc log while creating/opening. Check if you see any kind of integration.

Due christmas days, this will be covered next year i assume. 

Thanks, hopefully this can be fixed before the official release.

Looking at CSC I've found these (ERROR) lines being generated every time I do something over the SSL/TLS Inspection Tab:

DEBUG     Dec 24 10:54:57Z  [getvalidcacerts:23813]: log_exec: Command: /bin/certverify /conf/certificate/cacerts /conf/certificate/cacerts/Default.pem
ERROR     Dec 24 10:54:57Z  [getvalidcacerts:23813]: log_exec: Failed Command: /bin/certverify /conf/certificate/cacerts /conf/certificate/cacerts/Default.pem
DEBUG     Dec 24 10:54:57Z  [getvalidcacerts:23813]: log_exec: Command: /bin/certverify /conf/certificate/cacerts /conf/certificate/cacerts/SecurityAppliance_SSL_CA.pem
ERROR     Dec 24 10:54:57Z  [getvalidcacerts:23813]: csc_execve: Child exited with status 101
ERROR     Dec 24 10:54:57Z  [getvalidcacerts:23813]: log_exec: Failed Command: /bin/certverify /conf/certificate/cacerts /conf/certificate/cacerts/SecurityAppliance_SSL_CA.pem
INFO      Dec 24 10:54:57Z  [getvalidcacerts:23813]: create_act_out_perl_obj: varname=out
INFO      Dec 24 10:54:57Z  [getvalidcacerts:23813]: create_act_out_perl_obj: out.status=101
INFO      Dec 24 10:54:57Z  [getvalidcacerts:23813]: FORLOOP condition false
DEBUG     Dec 24 10:54:57Z  [getvalidcacerts:23813]: destroy_db_handle_pl: Destroying DBI DB handle.
INFO      Dec 24 10:54:57Z  [getvalidcacerts:23813]: opcode 'getvalidcacerts': time taken: 0.349907818 seconds

I couldn't find the reason on why this is happening, but I've managed to replicate It on a virtual machine.

One cool thing about this, if you try to create two rules with the same name, even that they don't show in the WebUI or work as expected, the interface will warn you there's already a rule with the same name.

This issue is being tracked with NC-83395.

The Dev team has been able to find the cause of this issue.

Here is a snippet from the e-mail I have received:

"The underlying cause has to do with using an apostrophe (as in Don’t) and using “Add rule above/below”.

After repairing the box, please do not create any rules with apostrophe in order to avoid this until we can get a fix."

Thanks for letting me track this down on your box, Prism.

It seems that when rules have special characters (such as apostrophe) and then do certain operations (Add below, move) there is a problem.  This also exists in 18.5, but the EAP always means people are changing and reconfiguring and trying new things which means it was hit a few times.

If anyone has this specific problem (cannot see any rules in the TLS Rules tab) please raise a ticket with Support and reference NC-79417.  If you cannot use support, you can send me a message in PM and I can repair their box.

Thanks for letting me track this down on your box, Prism.

It seems that when rules have special characters (such as apostrophe) and then do certain operations (Add below, move) there is a problem.  This also exists in 18.5, but the EAP always means people are changing and reconfiguring and trying new things which means it was hit a few times.

If anyone has this specific problem (cannot see any rules in the TLS Rules tab) please raise a ticket with Support and reference NC-79417.  If you cannot use support, you can send me a message in PM and I can repair their box.