-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial app start certificate error #293
Labels
bug
Something isn't working
Comments
Viir
added a commit
to pine-vm/pine
that referenced
this issue
Mar 22, 2024
To avoid crashes due to race condition as described at <natemcmaster/LettuceEncrypt#293>
Viir
added a commit
to pine-vm/pine
that referenced
this issue
Mar 23, 2024
Work around the problem with ASP.NET crashing because SSL certificates arrive ordered via LetsEncrypt arrive after starting the app. A similar issue was discussed at <natemcmaster/LettuceEncrypt#293> Also, update the LetsEncrypt library and Certes to integrate various recent upstream improvements.
Viir
added a commit
to pine-vm/pine
that referenced
this issue
Mar 23, 2024
Work around the problem with ASP.NET crashing because SSL certificates arrive ordered via LetsEncrypt arrive after starting the app: Disable HTTPS for a first start, if we find the certificate is not available. Later, if the HTTPS certificate has arrived, restart the ASP.NET host with the HTTPS URLS. For discussion of this issue, see: + <ffMathy/FluffySpoon.AspNet.EncryptWeMust#151> + <natemcmaster/LettuceEncrypt#293> Also, update the LetsEncrypt library and Certes to integrate various recent upstream improvements.
Viir
added a commit
to pine-vm/pine
that referenced
this issue
Mar 24, 2024
Work around the problem with ASP.NET crashing because SSL certificates arrive ordered via LetsEncrypt arrive after starting the app: Disable HTTPS for a first start, if we find the certificate is not available. Later, if the HTTPS certificate has arrived, restart the ASP.NET host with the HTTPS URLS. For discussion of this issue, see: + <ffMathy/FluffySpoon.AspNet.EncryptWeMust#151> + <natemcmaster/LettuceEncrypt#293> + <dotnet/aspnetcore#26258> + <dotnet/aspnetcore#45801> Also, update the LetsEncrypt library and Certes to integrate various recent upstream improvements.
Viir
added a commit
to Viir/FluffySpoon.AspNet.EncryptWeMust
that referenced
this issue
Mar 24, 2024
To help apps avoid crashing on race conditions as described at <natemcmaster/LettuceEncrypt#293>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hello, when the application starts for the first time e.g. in Docker, and there's no certificate to fallback I receive this error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I'd expect that Kestrel will expose HTTP endpoing and not throw any exception until the certificate is generated by the library.
The text was updated successfully, but these errors were encountered: