Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
getting socket timeout for node-forge npm package
-
Getting this error for only 1.3.1 and 1.3.0 versions. others are working fine. Any idea why?
This is happening randomly.
-
Hi @parthu-reddy ,
Unfortunately this will be difficult to troubleshoot.
As the NPM error indicates, this error is related to network connectivity. I'm afraid that neither the npm client nor the ProGet server is able to troubleshoot network problems, so you'll need to use something like Wireshark or another traffic monitoring tool to discover why you're getting that error.
ProGet does not crash with a network-level errors like that, which means it's something else that's causing the error. Most likely it's a load-blancer, firewall, etc.
There is also no reason that package 1.3.1 version or 1.3.0 would fail to download - but if that's indeed what's happening, then it's likely related to whatever device is issuing the network error. I have no explanation for what that would be.
As for the Azure screenshot, it's showing a a
200
(success) message, which means that ProGet is not giving any kind of errors. At least not all the time.Thanks,
Alana
-
Actually it's just postman to trigger APIs, pls check the versions. I triggered multiple versions, All of them got immediate response except for the 1.3.1 and 1.3.0. These two versions are failing sometimes. Will check with wireshark, pls check at your end as well.(there might be possibilities of missing headers that helps in closing socket or something like that.)
Actually this has nothing to do with npm client I guess. As I'm directly downloading the tgz from proget, which was causing error in npm client.
-
Hi @parthu-reddy ,
I created a new npm feed and had no problem downloading those package versions via npm.org.
As I mention, ProGet will not issue network errors, so it's definitely something else that's interfering. Hopefully you can find some information from Wireshark.FYI - in the screenshot you're sharing, I see most of the requests are going to registry.npmjs.org, and not to your proget server.
Thanks,
Alana
-
@atripp Ohh, sorry my mistake, changed it to proget, same problem actually. Will check at our end.