ASPNETCORE_ENVIRONMENT and HTTPS?

[plettb]

I'm really not sure if this is an issue or a question. I've run into some strange behavior and would like to understand it better and, if possible, get it working the way I'd like/expect.

In our application we have a number of projects that require different settings when running on Docker. We've been handling this by using a "SlowCheetah - like" process to transform our "appsettings.json" file. I wish I knew the right name for this feature, but essentially we have "appsettings.json", "appsettings.Development.json", and "appsettings.Docker.json" files. Changing the "ASPNETCORE_ENVIRONMENT" variable in the "docker-compose.override.yml" works beautifully for this. So far, all's well.

HOWEVER, when I change the environment variable, HTTPS stops working! There is some kind of magic that VS and/or Docker are doing when the environment variable is set to "Development" that I don't understand. With "Development" I see the certs created upon first run, and used correctly. When I change the environment variable, the certs still get created, but they don't get used - Kestrel refuses to start: "Message=Unable to configure HTTPS endpoint. No server certificate was specified...". There are numerous articles on the Internet on how to fix this specific problem, but I've had no luck making any of them work unless my environment is set back to "Development". Among other things, I've tried a variety of settings for "ASPNETCORE_Kestrel__Certificates__Default__Password" and "ASPNETCORE_Kestrel__Certificates__Default__Path" with no success.

Obviously, I'd like to use BOTH the environment variable and HTTPS. Any help would be much appreciated.

Thanks!
Brad.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3653642e-61ef-717b-5436-9bd0a3c4e6f4
• Version Independent ID: 80c1ce51-46fb-0693-525a-7cad37150c7b
• Content: Docker images for ASP.NET Core
• Content Source: aspnetcore/host-and-deploy/docker/building-net-docker-images.md
• Product: aspnet-core
• Technology: aspnetcore-hostdeploy
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[guardrex]

Hello @plettb ...

I'll strike my remark here after looking at the Docker article in the next comment. It doesn't address using a non-"Development" environment.

[guardrex]

Did you see this one? 👉 https://github.com/dotnet/dotnet-docker/blob/master/samples/run-aspnetcore-https-development.md

That looks like that guidance will help with the Docker HTTPS scenarios (I'm not a Docker Rex. 😄).

I'll close since we have the coverage and that Docker doc ☝️ is cross-linked. For additional support, we recommend the usual support channels ...

• Stack Overflow
• ASP.NET Core Slack
• ASP.NET Gitter

[guardrex]

@Rick-Anderson ... Need ur help on this one. The Docker doc doesn't clarify if Kestrel config is required when using a non-"Development" environment. That might be the case ... provide a normal Kestrel config in the app settings file (for the Docker environment) with the cert settings and then specify that environment name in the commands that they show. That might be what they intend for someone to do. However, it doesn't say so in https://github.com/dotnet/dotnet-docker/blob/master/samples/run-aspnetcore-https-development.md.

[plettb]

@guardrex I very much appreciate your help and the links, but it seems to me that until whatever magic the "Development" environment is doing to get certs working is documented, the issue shouldn't be closed. :)

P.S. The document you pointed me to looked very promising but I ended up having the same problems. Yes, this could be a DFU problem, but if it is I'd still like a little guidance and direction. ☺

[guardrex]

I re-opened it for further discussion. I agree with you that it's not clear.

They might want you to ...

1. Create a cert.
2. Set up a Kestrel section in your appsettings.Docker.json file with the cert config (following the guidance we have in the Kestrel topic)
3. Run the app like this ...

docker run --rm -it -p 8000:80 -p 8001:443 -e ASPNETCORE_URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=8001 -e ASPNETCORE_ENVIRONMENT=Docker ... {REMOVED THE REST} ...

... assuming port 8000 ... or change that to whatever port you'd be using.

Did you try something along those lines?

[guardrex]

I'm just suggesting that if you place the cert config in your appsettings.Docker.json file for Kestrel that it might fire right up and run on whatever cert you provide.

[plettb]

I'm just suggesting that if you place the cert config in your appsettings.Docker.json file for Kestrel that it might fire right up and run on whatever cert you provide.

That's exactly what I tried. So, for example, I put the following into my "appsettings.Docker.json" file:

  "Kestrel": {
    "Certificates": {
      "Default": {
        "Path": "/root/.aspnet/https/IdentityServer.pfx"
      }
    }
  }

With that I get a "Interop.Crypto.OpenSslCryptographicException", "Message=error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure".

(Without that I get "System.InvalidOperationException", "Message=Unable to configure HTTPS endpoint. No server certificate was specified...")