API requests - 404 error

If you use HTTPS to connect to your PRTG server, you must also use HTTPS in the API call.

How are you using the API call, is it in a VB or C# programm?

I am just running it from the PowerShell console. I am trying to figure out how it works. If I use HTTPS in the API call I receive the error regarding trust relationships.

Execute this beforehand:

# Ignore invalid SSL certs in a webrequest
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}

The PowerShell instance will then ignore certificates that are invalid for some reason.

[13]: C:\ 

> [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}

[14]: C:\ 

> Invoke-WebRequest "https://xxxxx/api/getsensordetails.xml?id=5025&username=myuser&passhash=0987654321"
Invoke-WebRequest : The underlying connection was closed: An unexpected error occurred on a send.
At line:1 char:1
+ Invoke-WebRequest "https://xxxxxx/api/getsensordetails.xml?id=5025&u ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Seems like my line isn't sufficient somehow. How about this one:

Add-Type @"
    using System.Net;
    using System.Security.Cryptography.X509Certificates;
    public class TrustAllCertsPolicy : ICertificatePolicy {
        public bool CheckValidationResult(
            ServicePoint srvPoint, X509Certificate certificate,
            WebRequest request, int certificateProblem) {
            return true;
        }
    }
"@
[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy

$result = Invoke-WebRequest -Uri "https://IpAddress/resource"

I found that solution, as well. I tried it with similar results. Here is the fiddler trace:

Session #12: The remote server (myserver) presented a certificate that did not validate, due to RemoteCertificateNameMismatch, RemoteCertificateChainErrors.

0 - A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


SUBJECT: CN=PRTG Demo Certificate, O=PRTG Demo Certificate
ISSUER: CN=PRTG Demo Certificate, O=PRTG Demo Certificate
EXPIRES: 7/6/2023 6:15:05 AM

(This warning can be disabled by clicking Tools | Fiddler Options.)  

I will work through the ssl certificate kb article, to try and resolve this.

Okay, let me know if you need further help :)