Error: Unable to get presigned websocket URL and connect to it

[edward-s]

After following the instructions, I am getting the following error: Error: Unable to get presigned websocket URL and connect to it, 403 http error code

Any clue on how to proceed?

TIA

[adieuadieu]

Hi @edward-s – Hm.. Did you set both the the endpoint URL and the API key displayed after you deploy the Proxy service to AWS? How are you setting them?

[toddwprice]

I believe this is the error I was getting after my first deploy because, in my case, the region in serverless.yml is set to eu-west-1 but my default profile is connected to a different region. I submitted a PR to add to the README to draw attention to the fact that this might need to be updated.

[edward-s]

@adieuadieu:
I filled in both endpoint URL and API key, via the Chromeless({remote}) constructor.
{ endPointUrl, apiKey }

@toddwprice:
I did that too, default was eu-west-1, and I changed it to us-east-1 (where all my other lambdas resides), but still same error

[toddwprice]

What commands did you run up through and including the one where the error occurs?

[edward-s]

I followed all the instructions in https://github.com/graphcool/chromeless/tree/master/serverless#installation, including changing the region to us-east-1

Successfully deployed proxy and got my lambda endpoint and api key

Tried to run the sample example with the endpoint and api key and got the above error

[edward-s]

So,

I tried again all the steps on another computer, same error.

Here's the error log, with my endpoint censored

{ HTTPError: Response code 403 (Forbidden)
    at stream.catch.then.data (/Users/edward/Documents/Projects/Temp/test/node_modules/got/index.js:182:13)
    at process._tickDomainCallback (internal/process/next_tick.js:129:7)
  name: 'HTTPError',
  host: 'rgyremovedrte0.execute-api.us-east-1.amazonaws.com',
  hostname: 'rgyremovedrte0.execute-api.us-east-1.amazonaws.com',
  method: 'GET',
  path: '/dev',
  protocol: 'https:',
  url: 'https://rgyremovedrte0.execute-api.us-east-1.amazonaws.com/dev',
  statusCode: 403,
  statusMessage: 'Forbidden',
  headers:
   { 'content-type': 'application/json',
     'content-length': '24',
     connection: 'close',
     date: 'Fri, 28 Jul 2017 02:20:50 GMT',
     'x-amzn-requestid': '5fa73e6f-733b-11e7-b962-3dc42990b753',
     'x-amzn-errortype': 'ForbiddenException',
     'x-cache': 'Error from cloudfront',
     via: '1.1 7158f458652a2c59cfcb688d5dc80347.cloudfront.net (CloudFront)',
     'x-amz-cf-id': 'removed-rnWqW9vnj-RYHIA==' } }
(node:66167) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1):

Error: Unable to get presigned websocket URL and connect to it.

[adieuadieu]

@edward-s Hm.. Could you try the following with curl, replacing the endpoint url and api key with your own:

curl -v --header "x-api-key: FSEMEOWHAT5HoAP3RKLOL5Tc0PNOPEzx4v7l9Yeu" https://XXXXXXX.execute-api.eu-west-1.amazonaws.com/dev/

Please share the result here. If you get a successful response, censor anything after X-Amz-Security-Token= in the response JSON url key.

Here's what a successful response would look like:

marco:chromeless marco$ curl -v --header "x-api-key: FSEMEOWHAT5HoAP3RKLOL5Tc0PNOPEzx4v7l9Yeu" https://XXXXXXX.execute-api.eu-west-1.amazonaws.com/dev/
*   Trying 52.222.163.16...
* Connected to XXXXXXX.execute-api.eu-west-1.amazonaws.com (52.222.163.16) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.execute-api.eu-west-1.amazonaws.com
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /dev/ HTTP/1.1
> Host: XXXXXXX.execute-api.eu-west-1.amazonaws.com
> User-Agent: curl/7.43.0
> Accept: */*
> x-api-key: FSEMEOWHAT5HoAP3RKLOL5Tc0PNOPEzx4v7l9Yeu
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 801
< Connection: keep-alive
< Date: Fri, 28 Jul 2017 09:04:47 GMT
< x-amzn-RequestId: ce652e5f-7373-11e7-ad7c-316ed70aee73
< X-Amzn-Trace-Id: sampled=0;root=1-597afe2f-0e1c7db8ebe9379793b53cc3
< X-Cache: Miss from cloudfront
< Via: 1.1 d12467f4c051603df707c4dfa0fee85d.cloudfront.net (CloudFront)
< X-Amz-Cf-Id: J0ggF4QiOCIoEtHZshw9sqIlpqx2OfSaKkq7SW1IbE8NECC-WbCBdQ==
<
* Connection #0 to host XXXXXXX.execute-api.eu-west-1.amazonaws.com left intact
{"url":"wss://a23dimeow2hrln.iot.eu-west-1.amazonaws.com/mqtt?X-Amz-Date=20170728T090447Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAJXXXXDIILOLHQ%2F20170728%2Feu-west-1%2Fiotdevicegateway%2Faws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=fdcba889a1e56bd8a4b6f3xxxxxx0862a4ccf2d9d8656c817b9ea9&X-Amz-Security-Token=FQoDYXdzEFoaDAAzvqwUgZIQvHsQfCL6AZp%2Bt%2F%2Baiy1ZUGPtkSP%2FAzMq5mbNRhdyUdkQ50b30dl1V26E9mYdC1OTiUUz9retc%2BF2SI6XXXXXXXXXBsy7lOS4TE0g6hBg9%2FAYWvheHAHAHAHAHAHAHAF6Q9cDZqjRcLBq3%2Fg%2FLoV%2F8rhqFMaUT3Wat9c2ttFnAwwUPIwSP%2BIz7BdrMb%2Bqn9lvuhwREuKI1xATqijHM3Okaf8aAaYIbN1vuHefyxe959mJLME3kXCHfJfQtzRmVDuXtnRg9NO%2BwogYTJcb1RPKFvHXXXXXXXXYjL%2Bh4BFfTWqft%2BMosPrrywU%3D","channelId":"cj5nn6jit000201p8swepfy20"}

[edward-s]

@adieuadieu: This is the response I get, 403 FORBIDDEN status code

I don't see any X-Amz-Security-Token

curl -v --header "x-api-key: tC28BT4NwU59censored1ON9R6mqEIMBe" https://rgcensorede0.execute-api.us-east-1.amazonaws.com/dev/
*   Trying 52.222.226.239...
* Connected to rgccensorede0.execute-api.us-east-1.amazonaws.com (52.222.226.239) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.execute-api.us-east-1.amazonaws.com
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /dev/ HTTP/1.1
> Host: rgcensoredte0.execute-api.us-east-1.amazonaws.com
> User-Agent: curl/7.43.0
> Accept: */*
> x-api-key: tC28BT4NwU5censored1ON9R6mqEIMBe
>
< HTTP/1.1 403 Forbidden
< Content-Type: application/json
< Content-Length: 23
< Connection: keep-alive
< Date: Fri, 28 Jul 2017 09:33:31 GMT
< x-amzn-RequestId: d1958903-7377-11e7-b5fa-bdbac4f904a6
< x-amzn-ErrorType: ForbiddenException
< X-Cache: Error from cloudfront
< Via: 1.1 c95065ab41censoerd6a4744fd4.cloudfront.net (CloudFront)
< X-Amz-Cf-Id: 73censored5G9l_Syxq8_A3-Ebq-gNccdensoredn1wg__IMpbsoKA==
<
* Connection #0 to host rgcensored0.execute-api.us-east-1.amazonaws.com left intact
{"message":"Forbidden"}

if it helps, going to the deployed proxy /dev/version path on the web browser gives me a successful response: {"chromeless":"1.0.0","serverlessChromeless":"1.0.0"}

[adieuadieu]

@edward-s thanks for that. I'm stumped.

Try removing the service and doing a fresh deploy. In the /serverless directory:

Remove the service from AWS:

./node_modules/.bin/serverless remove

Then re-deploy new:

npm run deploy

This will result in a new endpoint-url and api-key.

[edward-s]

I've tried on 2 different machines, both on different networks (Home & Office), AWS accounts and had slight different configurations (i.e, office machine is running OSX of 2 versions behind and generally less updated)

I have been doing many serverless lambda doing micro tasks, this project is the utility I'm truly excited about, too bad I can't run it :(

anyone who finds a solution, please help

[adieuadieu]

Hi @edward-s. Just pushed some changes. Could you pull the latest code from the repository and try deploying again? In our npm run deploy script, we were using the sls command. This command does not exist in ~/node_modules/.bin meaning the npm script was using a global version of Serverless—which, on your system, may not have been the latest version. The Chromeless Proxy requires at least serverless@0.16.0 because we need to create an AWS API Gateway Usage Plan in order to be able to use the API Key.