You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in the summer I set up a aspnetcore 2.0 project and everything pretty much worked out of the box. Now I've set up a 2.1 project and Kestrel immediately complains about not having certificates installed as part of its move toward HTTPS by default.
When not in a docker environment, this is fine. It's like 1 command to add the development certificates to work locally on your machine. But this issue isn't clearly explained, resolved, or automated when working with Docker.
What's the right path? Some say to not use HTTPS in docker (where your ingress point would strip off SSL for performance reasons) but I find that hard to believe as a best practice. Is there any way the documentation can discuss this?
Hello @killnine ... this is a duplicate of #6199 (with a little bit more discussion, perhaps overlap, on #3310). I'll close here, and you can track the work on #6199.
Back in the summer I set up a aspnetcore 2.0 project and everything pretty much worked out of the box. Now I've set up a 2.1 project and Kestrel immediately complains about not having certificates installed as part of its move toward HTTPS by default.
When not in a docker environment, this is fine. It's like 1 command to add the development certificates to work locally on your machine. But this issue isn't clearly explained, resolved, or automated when working with Docker.
What's the right path? Some say to not use HTTPS in docker (where your ingress point would strip off SSL for performance reasons) but I find that hard to believe as a best practice. Is there any way the documentation can discuss this?
Similar stackoverflow question: https://stackoverflow.com/questions/52167612/unable-to-create-a-dev-certificate-for-an-asp-net-core-web-app-in-a-docker-conta
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: