Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Upgrading from .Net Core 2.2 to 3.1, SSL and Docker .net core images

Upgrading from .Net Core 2.2 to 3.1, SSL and Docker .net core images

Scheduled Pinned Locked Moved ASP.NET
csharpasp-netdockercryptographyhelp
4 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jkirkerx
    wrote on last edited by
    #1

    Was forced to upgrade yesterday. Went to publish a Docker Container and the 2.2 images were no longer available. So I made it through the code changes; well at least I think I did, but can't run my web app because of the SSL error. I get the SSL connection not trusted error on both Firefox and Chrome. No option to ignore and accept the risk. Says my certificate is totally unsafe. Changed the project file to 3.1, upgraded NuGet packages. I tried IIS Crypto and set back to preferred. Did the Dotnet https clean and trust Installed Win64 OpenSSL to look at my localhost.pfx but can't really figure out how to use the program. I realize now that my startup.cs only loads Kestrel for running in a Docker container so my pfx files are not the issue. Ruled out HTTP1 or HTTP2 Issue two, finding the right Docker image to use in the container. I was using ... FROM microsoft/dotnet:2.2-aspnetcore-runtime AS base FROM microsoft/dotnet:2.2-sdk AS build Tried just changing the version number to 3.1, didn't work. Yesterday just from about 15mins of research, I changed to FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS base FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build But the build bombs; Can't remember why, I'll build it again. Fallback package Xamarin, That gives me something to go on ... 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: The "ResolvePackageAssets" task failed unexpectedly. [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: NuGet.Packaging.Core.PackagingException: Unable to find fallback package folder 'C:\Microsoft\Xamarin\NuGet\'. [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at NuGet.Packaging.FallbackPackagePathResolver..ctor(String userPackageFolder, IEnumerable`1 fallbackPackageFolders) [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(IEnumerable`1 packageFolders) [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at Microsoft.NET.Build.Tasks.NuGetPackageResolv

    J 1 Reply Last reply
    0
    • J jkirkerx

      Was forced to upgrade yesterday. Went to publish a Docker Container and the 2.2 images were no longer available. So I made it through the code changes; well at least I think I did, but can't run my web app because of the SSL error. I get the SSL connection not trusted error on both Firefox and Chrome. No option to ignore and accept the risk. Says my certificate is totally unsafe. Changed the project file to 3.1, upgraded NuGet packages. I tried IIS Crypto and set back to preferred. Did the Dotnet https clean and trust Installed Win64 OpenSSL to look at my localhost.pfx but can't really figure out how to use the program. I realize now that my startup.cs only loads Kestrel for running in a Docker container so my pfx files are not the issue. Ruled out HTTP1 or HTTP2 Issue two, finding the right Docker image to use in the container. I was using ... FROM microsoft/dotnet:2.2-aspnetcore-runtime AS base FROM microsoft/dotnet:2.2-sdk AS build Tried just changing the version number to 3.1, didn't work. Yesterday just from about 15mins of research, I changed to FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS base FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build But the build bombs; Can't remember why, I'll build it again. Fallback package Xamarin, That gives me something to go on ... 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: The "ResolvePackageAssets" task failed unexpectedly. [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: NuGet.Packaging.Core.PackagingException: Unable to find fallback package folder 'C:\Microsoft\Xamarin\NuGet\'. [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at NuGet.Packaging.FallbackPackagePathResolver..ctor(String userPackageFolder, IEnumerable`1 fallbackPackageFolders) [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at Microsoft.NET.Build.Tasks.NuGetPackageResolver.CreateResolver(IEnumerable`1 packageFolders) [/src/jkirkerx/jkirkerx.csproj] 1>/usr/share/dotnet/sdk/3.1.302/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error MSB4018: at Microsoft.NET.Build.Tasks.NuGetPackageResolv

      J Offline
      J Offline
      jkirkerx
      wrote on last edited by
      #2

      Its my computer. the browsers keep picking up an expired certificate when I run VS 2017 and 2019 I updated my localhost.pfx in my project that I use with Kestrel in a docker container. Oh it's been years since I had to deal with this. Just happy coding.

      If it ain't broke don't fix it Discover my world at jkirkerx.com

      J 1 Reply Last reply
      0
      • J jkirkerx

        Its my computer. the browsers keep picking up an expired certificate when I run VS 2017 and 2019 I updated my localhost.pfx in my project that I use with Kestrel in a docker container. Oh it's been years since I had to deal with this. Just happy coding.

        If it ain't broke don't fix it Discover my world at jkirkerx.com

        J Offline
        J Offline
        jkirkerx
        wrote on last edited by
        #3

        got it to work finally I added this to appSettings.json So now it uses the new pfx file that is not expired. I still wonder where the other file was coming from, perhaps somewhere in app data. And I didn't really program Kestrel to run in debug under the project name. Just for running in a Docker container. hmm....

        "Kestrel": {
        "Certificates": {
        "Default": {
        "Path": "localhost.pfx",
        "Password": ""
        }
        }
        }

        If it ain't broke don't fix it Discover my world at jkirkerx.com

        J 1 Reply Last reply
        0
        • J jkirkerx

          got it to work finally I added this to appSettings.json So now it uses the new pfx file that is not expired. I still wonder where the other file was coming from, perhaps somewhere in app data. And I didn't really program Kestrel to run in debug under the project name. Just for running in a Docker container. hmm....

          "Kestrel": {
          "Certificates": {
          "Default": {
          "Path": "localhost.pfx",
          "Password": ""
          }
          }
          }

          If it ain't broke don't fix it Discover my world at jkirkerx.com

          J Offline
          J Offline
          jkirkerx
          wrote on last edited by
          #4

          Now the Docker container builds, didn't have to change the images Had to do some adjustments on the startup.cs, and move some things around. So far so good.

          If it ain't broke don't fix it Discover my world at jkirkerx.com

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups