Help kaavali

[Fish]

1 hour ago, ramudu said:

apatlooo @Pitta medha nuvve kadha post lu vesav edo help ani , matter enti? 

Nenu kaadu andi 

[JollyReddy]

@Raazu 

[dasari4kntr]

3 minutes ago, Fish said:

The issue was happening when trying to install npm package 

firs...check do you have duplicates strict-ssl falg in config...as mentioned here...

44 minutes ago, dasari4kntr said:

 

npm config ls -l

ee command execute chese...any duplicate stric-ssl vunnyemo choodu...

sometimes..there will be multiple keys with same name...

 

if there is multiple keys...check the comments next to the keys...if there is no comment delete it...and maintain only only one flag...that is false...

next execute the below command as "export NODE_TLS_UNAUTHORIZED=0" 

3 minutes ago, movies_fan said:

If you want to fix in local for debugging, add NODE_TLS_UNAUTHORIZED=0 in env variable

 

next...set the strict-ssl flag as mentioned below..

1 hour ago, ramudu said:

delete ssl flag from  .npmrc and try run this again and see 

npm config set strict-ssl false

 

if that doesn't work , download cert file from npmjs and use set ca to that certificate path , before that if you are beyond corporate ***** , use your network id and password 

 

[Fish]

Thankyou all for the suggestions and really appreciate the quick responses

issue was resolved by upgrading node version to latest one  and also deleting strict SSL & reconfiguring

[Fish]

1 minute ago, dasari4kntr said:

firs...check do you have duplicates strict-ssl falg in config...as mentioned here...

next execute the below command as "export NODE_TLS_UNAUTHORIZED=0" 

 

next...set the strict-ssl flag as mentioned below..

 

Thankyou so much andi…..Yes there were duplicates, so removed all of them and reconfigured