Skip to content

_--- title: EndPoint Monitor - Documentation - Check Troubleshooting

Check Troubleshooting


  • Check for Element On Page not correctly identifying attribute value

    Sometimes the attribute value returned by the browser doesn't exactly match what is found on the DOM. This can be the case with attributes such as href or src where you may find the value you need to match against needs to be fully qualified, so the absolute URL rather than a relative link, even if that is what is presented on the DOM.
    For example, if you have a <img src=/assets/myimage.png /> and you want to check the value of the src attribute, you will need to set the Object Attribute Value to the full https://mysite.com/assets/myimage.png rather than just /assets/myimage.png.
    Additionally, the attribute value is automatically 'url decoded', so if you see it in the DOM as having url-encoded values like &amp; or &gt; then you need to match against them as their 'real' values, so & and < in these examples.


  • SSL/TLS error occurring on checks.

    EndPoint Monitor uses the trust store used by the Java installation its running under. You can use keytool to import any additional certificates required or to trust any self-signed certificates.
    https://docs.oracle.com/cd/E19906-01/820-4916/geygn/index.html

    If using an EndPoint Monitor managed Docker image then certificates added under the /opt/smnt/endPointMonitor/certs/ path will be automatically added when the image starts. More information can be found in the Configuration section.

    Web Journey checks additionally require the operating system running the browser to also have any self-signed certificates added. Information on doing this can be found on the below links:
  • (for Windows) https://learn.microsoft.com/en-us/skype-sdk/sdn/articles/installing-the-trusted-root-certificate
  • (for Ubuntu) https://ubuntu.com/server/docs/security-trust-store
  • (for RedHat) https://www.redhat.com/sysadmin/ca-certificates-cli