@neo0000 Moved from https://github.com/NuGet/Home/issues/6728
this looks like a server issue.
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):
NuGet version (x.x.x.xxx): 4.5.0.4685
dotnet.exe --version (if appropriate):
VS version (if appropriate): VS2017 version 15.5.6
OS version (i.e. win10 v1607 (14393.321)): win10 v1709
Worked before? If so, with which NuGet version: Worked before with same version: 4.5.0.4685
Thanks.
@neo0000, apologies for the slow response. Are you still experiencing the issue?
Hi @skofman1 ,
I have tried it a while ago and I could access it from a different network. Probably it is currently block in the office network. I talked to the person already to add it in their network whitelist and hopefully will try again later to access it again. Thanks.
Hi @skofman1 ,
Seems the problem is that the site is blocked in Hongkong(well I just found out today that we have an ISP here). The IT support team at the office tried to use a different ISP and it seems working well. I could access it using browser and Visual Studio NuGet manager.
Can you tell me the name of the ISP. We can work with our CDN provider to investigate.
Hi @skofman1 ,
Here is the ISP name: Telstra Hk
@neo0000 - I am reaching out to our CDN provider, it will be helpful if you can get us MTR logs from the machine that isn't able to access the service index. Please follow the steps here: https://docs.microsoft.com/en-us/nuget/policies/nuget-faq#nugetorg-not-accessible and send us the MTR log to [email protected], include my handle in the email to route to me.
Hi @shishirx34 ,
I already send an email to [email protected].
Thanks @neo0000 - received it. I have forwarded it to our CDN provider. Will keep you posted.
Hi @neo0000 - we need some additional information for CDN, please find the below request
It looks like the user's connection is not getting outside of his router possibly due to DNS resolution. If the user was to run the MTR to google.com or yahoo.com would he able to make a successful connection?
Could he attempt to run an MTR to an IP instead such as the APAC VIP for NuGet, 117.18.232.200?
Could you try running MTR against the above IP address? Also, can you verify that your connections to other websites(google.com/yahoo.com) are fine from the same machine?
Hi @neo0000 - I am still awaiting on the asks for the CDN. Is this not an issue anymore for you?
Hi @shishirx34
I was been busy and sorry about that, kindly check the images. I used the MTR with an ISP from HK
Thank you @neo0000. I have forwarded your findings to our CDN provider.
Welcome @shishirx34
Hi @neo0000, we got an update from the CDN folks. And it looks like the issue could possibly be on your end. See the response below:
I looked at the MTRs that you provided and I can see that we are blocked on that end.
As David(previous contact for CDN) had mentioned, it looks like the user's connection is not getting outside of his router possibly due to DNS resolution.
He can also check with his ISP to see if they are blocking us.
Last but not least, can you please provide the customer鈥檚 public IP address so we can also run MTRs from us to them?
I understand this is not really ideal, but do you mind mailing me the public IP address for your machine that faces this issue. You can email us on [email protected] if you are uncomfortable sharing the IP here. Also, can you check with your ISP, if possible, that they are somehow blocking nuget.org(CDN)
@neo0000 - just following up, is this still an issue?
Hi @shishirx34 ,
Will ask the IT support team if it is possible to consult with our ISP from HK. I'll send an update here, thanks.
Hi @shishirx34 ,
Do you guys have a location restriction?
Hi @shishirx34 ,
Seems that we have found the problem. The IT team just noticed today that the IP: 117.18.232.200 is blocked using the HK ISP. Also the said IP is also use for windows update, currently they are using a different ISP if they would like to update their systems here. So now they allow my desktop to access it in both ISP's.
You may close the issue and thank you for the effort to solve the problem.
Thats good news. I am glad the issue is resolved. Feel free to reach out to us if you have any trouble with the service.
Most helpful comment
@neo0000, apologies for the slow response. Are you still experiencing the issue?