`Getting app info... Creating app with these attributes... + name: scp_iot_proxy path: scp_iot_proxy routes: + scpiotproxy.cfapps.eu10.hana.ondemand.com Creating app scp_iot_proxy... Mapping routes... Comparing local files to remote cache... Packaging files to upload... Uploading files... 1.16 KiB / 1.16 KiB [======================================================================================================================================================================] 100.00% 1s Waiting for API to complete processing files... Staging app and tracing logs... Downloading sap_java_buildpack... Downloading nodejs_buildpack... Downloading staticfile_buildpack... Downloading java_buildpack... Downloading ruby_buildpack... Downloaded nodejs_buildpack Downloading go_buildpack... Downloaded sap_java_buildpack Downloading python_buildpack... Downloaded ruby_buildpack Downloading php_buildpack... Downloaded go_buildpack Downloading binary_buildpack... Downloaded python_buildpack Downloading dotnet_core_buildpack... Downloaded java_buildpack Downloaded binary_buildpack Downloaded dotnet_core_buildpack Downloaded php_buildpack Downloaded staticfile_buildpack Creating container Successfully created container Downloading app package... Downloaded app package (1.2K) -----> Nodejs Buildpack version 1.6.12 -----> Installing binaries engines.node (package.json): unspecified engines.npm (package.json): unspecified (use default) **WARNING** Node version not specified in package.json. See: http://docs.cloudfoundry.org/buildpacks/node/node-tips.html -----> Installing node 4.8.6 Download [https://buildpacks.cloudfoundry.org/dependencies/node/node-4.8.6-linux-x64-c8323162.tgz] Using default npm version: 2.15.11 -----> Installing yarn 1.2.1 Download [https://buildpacks.cloudfoundry.org/dependencies/yarn/yarn-v1.2.1-a16106e2.tar.gz] Installed yarn 1.2.1 -----> Creating runtime environment PRO TIP: It is recommended to vendor the application's Node.js dependencies Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring NODE_ENV=production NODE_HOME=/tmp/contents664282185/deps/0/node NODE_MODULES_CACHE=true NODE_VERBOSE=false NPM_CONFIG_LOGLEVEL=error NPM_CONFIG_PRODUCTION=true -----> Restoring cache Skipping cache restore (no previous cache) -----> Building dependencies Installing node modules (package.json) npm ERR! fetch failed http://nexus.wdf.sap.corp:8081/nexus/repository/build.milestones.npm/brace-expansion/-/brace-expansion-1.1.8.tgz npm ERR! fetch failed http://nexus.wdf.sap.corp:8081/nexus/repository/build.milestones.npm/boom/-/boom-2.10.1.tgz npm ERR! fetch failed http://nexus.wdf.sap.corp:8081/nexus/repository/build.milestones.npm/builtin-modules/-/builtin-modules-1.1.1.tgz` ....... npm ERR! Linux 4.4.0-108-generic npm ERR! argv "/tmp/contents448755304/deps/0/node/bin/node" "/tmp/contents448755304/deps/0/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/app/.npmrc" "--cache" "/tmp/app/.npm" npm ERR! node v4.8.6 npm ERR! npm v2.15.11 npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! syscall getaddrinfo npm ERR! network getaddrinfo ENOTFOUND nexus.wdf.sap.corp nexus.wdf.sap.corp:8081 npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Please include the following file with any support request: npm ERR! /tmp/app/npm-debug.log **ERROR** Unable to build dependencies: exit status 1 Failed to compile droplet: Failed to run all supply scripts: exit status 14 Exit status 223 Stopping instance 93c9eb92-07fd-4bb7-9c43-24b5ca0ad400 Destroying container Successfully destroyed container FAILED Error restarting application: BuildpackCompileFailed`