Troubleshoot the HTTP Error 403 (Forbidden) for Jenkins

Troubleshoot the HTTP Error 403 (Forbidden) for Jenkins

When installing the Jenkins monitoring plugins, you may encounter the following error:
HTTP Error 403: Forbidden: This error usually indicates that you don't have the necessary permissions to access a particular resource or perform a specific action in your Jenkins environment.

Follow the steps below to troubleshoot the issue.
  1. Inspect the API key and credentials in the .cfg file: Ensure that you are using the correct API key and credentials in the plugin .cfg file so that the plugin can communicate with your Jenkins instance.

  2. Check Jenkins server status: Ensure that the Jenkins server is running, so that the server where the plugin and the Site24x7 server agent is installed is able to access Jenkins. A "502 Bad Gateway" error can occur if Jenkins is down or experiencing issues.
    You can test the Jenkins URL in the server where Site24x7 server agent is installed to know the Jenkins server status:
    curl http://jenkins-server:port/metrics/
Once you've made changes based on the checks above, restart the Site24x7 server monitoring agent or re-register the plugin. Within five minutes, you should be able to view performance metrics in Site24x7.
If the issue persists, reach out to support@site24x7.com with the plugin details.