Home: Certificate error on https://nuget.smbsrc.net

[FeodorFitsner]

Getting an error while pushing symbols package with NuGet 4.1 command-line client on Windows:

An error was encountered when fetching 'PUT https://nuget.smbsrc.net/'. The request will now be retried.
An error occurred while sending the request.
  The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
  The remote certificate is invalid according to the validation procedure.

Opening https://nuget.smbsrc.net in the browser confirms the problem with certificate.

[mishra14]

cc @skofman1

[anangaur]

@FeodorFitsner, thanks for letting us know. We have passed on this information/feedback to SymbolSource.org.

[fredericDelaporte]

As written here, it is possible to work around this certificate expiration by going through http instead...

nuget push dist/MyPackage.1.0.0.symbols.nupkg -Source http://nuget.smbsrc.net  -ApiKey [my key]

Of course this then means the thing goes un-encrypted over the Internet, likely the API key too. (Unless some application level ciphering is done by NuGet on it.)

[FeodorFitsner]

Is there any update guys? I can't believe installing a new certificate could take so long. Is there any way to approach SymbolSource.org maintainers directly?

[pavkam]

Still errs out. Any progress?

[rrelyea]

We have passed this info to the symbolsource folks, but haven't gotten a response.

[mishra14]

Folks, please see https://github.com/NuGet/Home/issues/6101 for a potential fix to this problem.

[anangaur]

@mishra14 that's not a fix to the problem but rather a way out to not fail CI builds on secondary push to SymbolSource.
However, the auto-push experience is not right especially in failure scenarios. There is another proposal to disintegrate the current overloaded push to just do an atomic operation of pushing packages to one source: https://github.com/NuGet/Home/issues/6113
If we implement https://github.com/NuGet/Home/issues/6113, I feel https://github.com/NuGet/Home/issues/6101 would no longer be required.

[FeodorFitsner]

Looks like the certificate was updated.

[anangaur]

Closing this issue now as the cert was renewed. Nevetheless, we plan to stop auto-push of packages to SymbolSource as announced here: https://github.com/NuGet/Announcements/issues/13

[evadelnuevo]

It seems the certificate expired again

[bilal-fazlani]

It's expired again

[FeodorFitsner]

Yep, publishing of symbol packages from AppVeyor builds is not working.

[skofman1]

If you are publishing portable PDBs take a look at the NuGet hosted Symbol server: https://blog.nuget.org/20181116/Improved-debugging-experience-with-the-NuGet-org-symbol-server-and-snupkg.html

[CarlosLanderas]

We are having trouble as well

[unaizorrilla]

One year later, certificate is expired again....

[yevhen]

C'mon ((

[JoshClose]

Use @skofman1's suggestion. That worked for me.

[FeodorFitsner]

@skofman1 Am I correct to assume .snupkg is doable from/with VS 2017 only or is it the latest nuget.exe that works with VS 2015 too?

[skofman1]

@FeodorFitsner , the blog provides all the details on this. You will need to build your code using VS 2017 15.9 to generate the PDBs. There were changes to the compiler in 15.9 that are required.

[FeodorFitsner]

OK, what about VS 2015 support with "old" symbol packages?

[JoshClose]

I'm using VS 2015 but building with dotnet pack using the latest dotnet core.

[FeodorFitsner]

Right, but I'm talking about "traditional" .NET Framework apps.

[JoshClose]

I build netstandard2.0 and net 45 using dotnet pack

<TargetFrameworks>netstandard2.0;net45</TargetFrameworks>

[weitzhandler]

Same problem here.

[fredericDelaporte]

In other words, the certificate has expired again. That is the third time it expires without being renewed on time. Isn't this slightly deceptive?

[anangaur]

Checkout NuGet symbol server: https://blog.nuget.org/20181116/Improved-debugging-experience-with-the-NuGet-org-symbol-server-and-snupkg.html

[FeodorFitsner]

...and if you are deploying from AppVeyor .snupkg publishing was implemented in AppVeyor long time ago.

[fredericDelaporte]

@anangaur, @FeodorFitsner , the new symbol system is very likely to be well known by most people here, and that is not the subject.

Letting a certificate expiring without renewing it is no way of obsoleting a feature previous version.
Beside, there is also legacy versions of software which may need some new release, notably for fixing security issues, while the code base of those legacy versions is very likely not updated to be able to publish snupkg.

[FeodorFitsner]

@fredericDelaporte I agree. I'm not sure I understand who is standing behind that web site, who is responsible for its maintenance?