- attached 2018-11-30T08_33_00_685Z-debug.log
Problem installing idb-connector
Hi,
I'm facing a problem trying to install idb-connector through npm 6.4.1 and node 10.11.0 on IBM i V7R3M0. The output from calling npm i idb-connector and the resulting debug log are attached to this ticket. Is there anything I'm missing or doing wrong?
Thanks for your help and best regards, Andreas
Comments (8)
-
reporter -
reporter - attached npm-i-idb-connector.txt
-
reporter - edited description
-
Account Deactivated Hello @doan23 , Is your system able to manually download the package ? You may verify it by running --
wget --no-check-certificate https://bitbucket.org/litmis/nodejs-idb-connector/downloads/db2ia-v1.1.4-node-v64-ibmi-ppc64.tar.gz
If the package can be downloaded, it would be a firewall issue because I saw this line in the log -->
node-pre-gyp WARN Hit error Hostname/IP does not match certificate's altnames: Host: bbuseruploads.s3.amazonaws.com. is not in the cert's altnames: DNS:*.blue-shield.at, DNS:blue-shield.at
I am not sure how to resolve the problem by now, but you may try this --
NODE_TLS_REJECT_UNAUTHORIZED=0 npm i idb-connector
-
Account Deactivated -
assigned issue to
-
assigned issue to
-
reporter Hi @mengxumx ,
thanks a lot for your support! I missed the part "DNS:blue-shield.at". Our companies internet access is being protected by using DNS servers from blue-shield.at and obviously bbuseruploads.s3.amazonaws.com got flagged with "Malware Zero Day". Thus, when I try opening one of the download URLs, I always end up at a page telling me that access is blocked.
We'll get in contact with Blue Shield in order to get the URL whitelisted. Let's see how that works out.
-
reporter Hi @mengxumx ,
Blue Shield updated their settings and the command
npm i idb-connector
is working again like expected when being called from our companies network.Once again, thanks for your support, the ticket is resolved.
-
reporter - changed status to resolved
The problem was caused by our DNS provider.
- Log in to comment