Home
Options

LinqPad 5 Nuget - Unable to connect to the remote server

llambertllambert
edited March 2016
Searching works fine but I am getting the following where when I click "Add to Query"

Error downloading 'log4net' - Unable to connect to the remote server

I've tried several different packages and they all fail the same way.

Nuget works fine in LinqPad 4 and Visual Studio 2013. Anyone else run across this problem?
· Share on FacebookShare on Twitter

Comments

  • Options
    sgmooresgmoore
    Not exactly the same, but I started getting '404 Not Found' errors when attempting to update any Nuget package. This turned out to be my own fault as I had added a second Package source which was no longer working. (Even though this source was lower priority that the official source, it stopped all updates from working)
    · Share on FacebookShare on Twitter
  • Options
    llambertllambert
    I do have a second package source. That package source works fine in VS2013 but appears to break LinqPad 5. Probably some issue with Nuget V3 ?
    · Share on FacebookShare on Twitter
  • Options
    JoeAlbahariJoeAlbahari
    Is your Internet connection via a proxy?
    · Share on FacebookShare on Twitter
  • Options
    llambertllambert
    No proxy involved. The second repo is on site, I have a few custom packages in it.
    · Share on FacebookShare on Twitter
  • Options
    kingkeithkingkeith
    Just posting in case this information helps anyone.

    I had a similar problem, in that I had a package source which was no longer working, that prevented me from downloading/updating any packages from the official source. Unticking the bad source resolved the problem for me. The error I was getting was:

    ---------------------------
    LINQPad
    ---------------------------
    Error downloading 'PackageNameHere' - The remote server returned an error: (401) Unauthorized.
    ---------------------------
    OK
    ---------------------------

    My internet connection is via a proxy, which LINQPad auto detects. (Although the bad package source was on the LAN.)
    · Share on FacebookShare on Twitter
  • Options
    llambertllambert
    I disabled the other repo and it is working fine now.
    · Share on FacebookShare on Twitter
  • Options
    vyzavyza
    edited August 2017
    Sorry, wrong thread
    · Share on FacebookShare on Twitter
Sign In or Register to comment.