Connection reset by peer

I'm trying to get going with the WorldCheckOneApi, but I'm unable to even make a proper connection to the server.

For example, using the Postman "SEQ-1a: Get my top level groups", I always get "Could not get any response. The request from Postman is as follows (I have removed the key / signature)

GET /groups HTTP/1.1
Host: rms-world-check-one-api-pilot.thomsonreuters.com
Date: Tue, 14 Feb 2017 16:36:48 GMT
Authorization: Signature keyId="<< REMOVED >>",algorithm="hmac-sha256",headers="(request-target) host date",signature="<< REMOVED >>"

I have done this on both Pilot and production environments, and the same things happens.

I have also tried a

wget https://rms-world-check-one-api-pilot.thomsonreuters.com/

and I get

Connecting to rms-world-check-one-api-pilot.thomsonreuters.com|159.220.25.95|:443... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.

Or doing...

curl https://rms-world-check-one-api-pilot.thomsonreuters.com/groups

gives me

curl: (56) SSLRead() return error -9806

In case it's some network issue, doing

traceroute rms-world-check-one-api-pilot.thomsonreuters.com

results in

traceroute to rms-world-check-one-api-pilot.thomsonreuters.com (159.220.25.95), 64 hops max, 52 byte packets
 1  10.1.16.1 (10.1.16.1)  3.257 ms  1.845 ms  1.275 ms
 2  no-dns-yet.convergencegroup.co.uk (109.232.61.194)  2.937 ms  5.631 ms  5.110 ms
 3  * * *
 4  10.200.0.70 (10.200.0.70)  5.521 ms  2.519 ms  4.941 ms
 5  10.200.0.61 (10.200.0.61)  2.787 ms  2.921 ms  2.780 ms
 6  137.221.191.44 (137.221.191.44)  2.669 ms  2.530 ms  2.450 ms
 7  te-4-3.car5.london1.level3.net (217.163.45.205)  2.578 ms  4.584 ms  4.185 ms
 8  * thomson-fin.edge6.london1.level3.net (212.187.200.122)  6.410 ms  8.616 ms

Thanks!

Find more posts tagged with

connection

world-check-one

trace

tcp

world-check

Accepted answers

edo

I've got it... I missed the

/v1/

In the URL.

It would be good to have a better error I think than something that is at the TCP level. Maybe a 404?

All comments

brian.bourgault

Hi @edo,

I tested your credentials using Postman and it is working....

If you could email me the output of the "Code" in Postman with your <<REMOVED>> data, then I can help you...

Hope this helps,
Brian

[
  {
    "id": "<REMOVED>",
    "name": "Acme Services Ltd (Pilot)",
    "parentId": null,
    "hasChildren": true,
    "status": "ACTIVE",
    "children": [
      {
        "id": "<REMOVED>",
        "name": "Acme Services Ltd (Pilot) - Screening",
        "parentId": "<REMOVED>",
        "hasChildren": false,
        "status": "ACTIVE",
        "children": []
      }
    ]
  }
]

edo

I've got it... I missed the

/v1/

In the URL.

It would be good to have a better error I think than something that is at the TCP level. Maybe a 404?

EXPLORE OUR SITES