Has anyone else seen this? I just installed a fresh Chef-compliance server on a new Centos 7 host (chef-compliance-1.7.7-1.el7.x86_64.rpm) and upon adding a node and attempting to run an ad-hoc scan, nothing appears to happen in the UI, however tailing the logs shows that the scan is indeed running. Also once a scheduled scan has completed, and I get results in the UI, I am unable to open the reports link. I initially thought that I had something configured incorrectly with either my Chef integration or with connection to Automate, so I reverted the VM and reinstalled compliance with no connectivity to Chef-server or Automate and still am getting the same behavior. Thoughts anyone?