Troubleshooting Brand Reputation Monitor
The Brand Reputation Monitor uses Google's Web Risk API for data collection. Therefore, Google services must be reachable from the server where Applications Manager is installed in order for the monitor to collect data.
Error : Web Risk API is not reachable
-
Test API Accessibility: Verify that the Web Risk API is accessible from the Applications Manager server.
-
Proxy Server Configuration: If your environment requires the use of a proxy server to access the Web Risk API, configure the proxy in Applications Manager. To learn how to configure the proxy, [click here].
-
Bypass Proxy for Web Risk API: If you have configured a proxy in Applications Manager but want to bypass it for the Web Risk API domain (webrisk.googleapis.com), add the domain name under the "Do not use proxy for addresses beginning with" section in the "Configure Proxy" page: Navigate to Settings > Product Settings > Proxy Server Settings.
Applications Manager installed on servers in locations where Google services are inaccessible cannot have Brand Reputation monitor. List of counties where Google services are available.
Still facing issues?
If the problem persists, contact our support team along with the following details:
-
A screenshot of the "Add Monitor" page.
-
Access the Web Risk API in a browser and share a screenshot of the response.
-
Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...PHP Monitor Troubleshooting
PHP Monitor Errors and Troubleshooting Guide Check if the phpstats.php file in the webserver's document root. Ensure there is no modifications done in phpstats.php file Check if the correct PHP path is given. Retry with the "SSL is enabled" option ...