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!

Proget npm feed using HTTP/80 when configured to use HTTPS



  • Hi!

    I have an npm-feed i ProGet configured with the connector URL: https://registry.npmjs.org. However, when I try to download packages using this ProGet npm feed, Proget seemingly tries to communicate to registry.npmjs.org on port 80. I only have port 443 open in my outgoing firewall, so this connection attempt fails (and I would like to keep port 80 closed):

    System.Net.WebException: Unable to connect to the remote server ---> 
      System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, 
      or established connection failed because connected host has failed to respond 151.101.84.162:80
    at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, 
      Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
    

    A get request to download a package from an address like this:

    http://<internal proget server>/npm/npm-external/css-selector-tokenizer/-/css-selector-tokenizer-0.7.0.tgz
    

    I get this back from the server (and an entry of the error above in the ProGet logs) :

    {"error":"WebException","reason":"Unable to connect to the remote server"}
    

    This does not fail for all packages, but random packages seems to fail each time I clear the ProGet package cache and try to reinstall packages.

    Product: ProGet
    Version: 4.8.2


  • inedo-engineer

    You will need to open both ports; the npm api uses both HTTP and HTTPS.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation