FetchError: request to https://..../WsWorkunits/WUQuery.json failed, reason: unable to get local issuer certificate

[lpezet]

Hello!

Sigh, I'm back at it again.
This time I have a CA-issued SSL certificate (from AWS) and yet I can't see my workunit result in the "HPCC" panel.
When I opened the Webview from the Developer Tools, I saw this error:

FetchError: request to https://..../WsWorkunits/WUQuery.json failed, reason: unable to get local issuer

None of the tricks we mentioned in #271 work.
All I can find googling this error is http proxy (which I don't use) and git related stuff.

Any ideas?

[lpezet]

Here's the very short stack trace from Developer Webview:

stack trace: FetchError: request to https://xxxxxx:18010/WsWorkunits/WUQuery.json failed, reason: unable to get local issuer certificate 
at ClientRequest.<anonymous> (/Users/lucpezet/.vscode/extensions/hpcc-systems.ecl-2.16.5/dist/extension.js:2:535981) 
at ClientRequest.emit (events.js:315:20) 
at TLSSocket.socketErrorListener (_http_client.js:469:9) 
at TLSSocket.emit (events.js:315:20) at emitErrorNT (internal/streams/destroy.js:106:8) 
at emitErrorCloseNT (internal/streams/destroy.js:74:3) 
at processTicksAndRejections (internal/process/task_queues.js:80:21)

[GordonSmith]

Are you able to open ECL Watch in browser?

[GordonSmith]

Also try enabling ecl.forceProxySupport in your settings.

[lpezet]

@GordonSmith I am able to open ECL Watch in browser without any errors or even warnings.
I ticked the ecl.forceProxySupport setting to no avail.

[GordonSmith]

@lpezet - would it be possible to get access to this setup to test against?

Did you say you were able to submit ECL via VSCode just couldn't view the results?

[lpezet]

@GordonSmith That is correct. I can submit just fine, I just can't see the results in the "HPCC" panel (I just get the spinning "Loading" animation forever).
This is a work setup so, as is, it's not possible to grant access to it. I'll try to re-create it so I can grant access to it.
Thanks for helping out @GordonSmith!

[GordonSmith]

@lpezet can you sanity check you have the latest version of the ECL Extension, as the last release contained some code which ensures the same communications pipe is used for the results page as the submit logic. (Prior to that it was calling directly from the results page - an embedded iframe - to the ESP)?

[GordonSmith]

And if you are on latest can you check with v2.16.1 (the prior version without the new pipe mentioned above)?

[lpezet]

@GordonSmith Oh wow! That's it! I switched to 2.16.1 and results would show in the HPCC panel. Results are then not showing anymore for any version after that (I tried every version from 2.16.2 to 2.16.5).

[GordonSmith]

Hmmm - ok thanks I can investigate now - I might make that pipe an option as its only needed when targeting a non SSL env from a web hosted version of VSCode (hosted on https - gitpod.io).

[GordonSmith]

@lpezet what server version are you using - I am scratching my head as to why this is not working... In theory the new version should have a better chance of working with self signed certs than the older version.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.