I am testing one of the base PowerShell examples and I get the following error:
Invoke-WebRequest : {"Data":null,"Meta":{"TotalCount":0,"ResponseCode":500,"ErrorMessage":"The remote name could not be resolved: 'ws0.pulseway.com'"}}
At C:\CVSSource\pulseway_salesforce_connector\test.ps1:9 char:13
I just created this token so I don't think an old token is the issue. It seems like there could be a DNS routing or resolution issue on the Pulseway side, at least maybe for our hosted instance.
Hi guys,
I am testing one of the base PowerShell examples and I get the following error:
Invoke-WebRequest : {"Data":null,"Meta":{"TotalCount":0,"ResponseCode":500,"ErrorMessage":"The remote name could not be resolved: 'ws0.pulseway.com'"}}
At C:\CVSSource\pulseway_salesforce_connector\test.ps1:9 char:13
+ $response = Invoke-WebRequest -Uri 'https://api.pulseway.com/v3/devic ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
I just created this token so I don't think an old token is the issue.
It seems like there could be a DNS routing or resolution issue on the Pulseway side, at least maybe for our hosted instance.
Any help is greatly appreciated. Thank you.