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.
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:
or, if you have just a domain in your URL just do
or, for multiple FQDN's use:
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
and ensure no
opsview-xxx packages are mentioned. If they are, check your repository configuration files (by default, either
/etc/apt/sources.d/opsview.list) to ensure the correct full version number is specified in the URL (for example, so use
184.108.40.206301181814 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: