Opsview - Cannot Run Reports "the content is blocked contact the site owner to fix the issue"

Symptoms

• Reports will not run in Opsview Monitor 6.7.2 and later, and users are presented with "The content is blocked.  Contact the site owner to fix the issue" (usually happens after an upgrade)
  -  Browser Developer Tools will show similar behaviour to:

Cause: Enhanced Security

Opsview Monitor protects itself from spurious HOST headers in the HTTP requests when it redirects to HTTPS.  One of the protections is to prevent browser communication using a server address that doesn't match the Opsview server hostname (to prevent man-in-the-middle attacks).

Solution: Update user_vars.yml

The server name used in the URL must be added to the Opsview configuration, so it will be accepted as a known and valid address.  Specify the server address or addresses as below; just remember that you do not need to put in the full URL, just the server address.

As the root user, backup, and modify the /opt/opsview/deploy/etc/user_vars.yml file to add or amend the following parameter. 

For a single FQDN use:

opsview_webserver_external_address: "opsview.mydomain.com"

or, if you have just a domain in your URL just do

opsview_webserver_external_address: "mydomain"

or, for multiple FQDN's use:

opsview_webserver_external_address:
  - "opsview.mydomain.com"
  - "another.myotherdomain.com"

At this point the Orchestrator playbook will need to be run to apply the changes.  However, the playbook will also update any available Opsview packages on your system (due to how your server repositories are configured) which can introduce more problems.

To check against this, run

yum check-update

or

apt-get update

and ensure no opsview-xxx packages are mentioned.  If they are, check your repository configuration files (by default, either /etc/yum.repos.d/opsview.repo or /etc/apt/sources.d/opsview.list) to ensure the correct full version number is specified in the URL (for example, so use 6.8.0.202301181814 rather than 6.8, to match your Opsview installation).

After ensuring your repository configuration is correct and there are no Opsview package updates available, you can then run the Orchestrator playbook as the root user to apply the configuration change and restart the required processes:

/opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/orchestrator-install.yml

You can then reload your web browser pages to prove the error is resolved.

If you have any issues

• Please contact our team via the chat service box available on any of our websites or via email to support@itrsgroup.com
  

Make sure you provide us with:

• - ANY LOG FILE OR DIAGNOSTIC DATA
• - ANY SCREENSHOT
• - ANY VENDOR/VERSION etc