Skip to Content

public npm registry not accessible after upgrade to HANA 2.0 sp3


After upgrading to HANA 2.0 sp3 I am unable to access the npm registry.

My UPSTREAM_LINK env is set to (same as in SP 2) and no HTTP_PROXY env is set because it is not required in the server. (I am able to access through curl without any proxy setting).

The error I received is

http  --> ERR, req: 'GET', error: unable to get local issuer certificate (connecting to

All the settings were same as in sp2.

Any help is appreciated.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on May 31, 2018 at 12:00 PM

    This could help:

    xs unbind-service di-local-npm-registry devx-npm-cache-fs
    xs delete-service devx-npm-cache-fs

    xs create-service fs-storage free devx-npm-cache-fs
    xs bind-service di-local-npm-registry devx-npm-cache-fs

    xs restage di-local-npm-registry
    xs restart di-local-npm-registry

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.