Basic Sidekick build failed due to signed certificate failure

[mpilija]

Please, provide the details below:

Did you verify whether this issue has already been reported here?

Maybe - only thing related found was this: https://github.com/NativeScript/sidekick-feedback/issues/131

Tell us about the problem

I'm unable to perform cloud build with following error: Build failed. Self signed certificate in certificate chain.

Which platform(s) does the issue occur on?

Android Windows

Provide the following version numbers that the issue occurs with:

Everythings was taken latest.

Tell us how to recreate the issue in as much detail as possible

1. Open NativeScrppit Sidekicj or Visual Studio 2017 with Sidekick plugin and just click on build. In both IDE same error occurs

Just to mention that proiject is buildable via NativeScript CLI.

Does this issue happen every time?

Yes

Send the client logs

console_18-07-20_11-56-21.374 (1).log console_18-07-20_11-56-21.374.log main_18-07-20_11-56-22.199.log prerequisites_18-07-20_11-56-33.108.log

[ventsislav-georgiev]

@mpilija This issue usually occurs when the PC is behind a corporate proxy and Strict SSL is enabled. Could you check the Proxy settings in VS2017 -> Tools -> Options and disable Strict SSL (VS restart is required):

You can also manually try setting the environment variable: NODE_TLS_REJECT_UNAUTHORIZED=0 to force node to accept self-signed certificates (PC restart may be required for the new env to be picked up).

[mpilija]

@ventsislav-georgiev that optional was already disabled:

Still not able to perform build.

[ventsislav-georgiev]

@mpilija did you try to set NODE_TLS_REJECT_UNAUTHORIZED=0 in the environment variables?

[mpilija]

@ventsislav-georgiev yes, i did, same result. also, when trying to build via sidekick desktop application, same thing happen:

[ventsislav-georgiev]

@mpilija since it is working via the CLI, could you check what is the output of the tns proxy command?

[mpilija]

@ventsislav-georgiev it's working for local build but for cloud it doesn't. for command tns login i get same error:

however, browser shows that login was successfull:

[ventsislav-georgiev]

@mpilija it seems that you are behind a proxy which we cannot detect automatically and you need to manually configure it for example via the tns proxy set command with the --insecure param. You need to set the proxy url and provide an username and password if your proxy requires authentication.

[mpilija]

@ventsislav-georgiev there were some web filters on our gateway that blocked required content. we set policy to allow required connections to perform build and it's working now. thank you for support.

[teobugslayer]

I am glad the issue was resolved successfully.