-
Notifications
You must be signed in to change notification settings - Fork 200
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
Cannot get Https Working #13
Comments
I also faced the same issue. Only through http it is accessible. https not working in azure. |
I am facing the same problem with Https step. Please help |
Is there any update on HTTPS endpoint fix? I am getting the same error. |
I was getting the same error after service fabric cluster creation. Following the "Give NETWORK SERVICE access to the certificate's private key" step resolved the issue. You can remote desktop into your service fabric node, run "certlm.msc" from Start Menu, right click on a service fabric certificate and choose "All Tasks -> Manage Private Keys..." option. In the dialog that opens, under Security tab, in Group or user names group-box, select NETWORK SERVICE if present or add it using the "Add..." button if absent and grant it "Full control" as shown in the attachment. We may not have to do these steps for all certificates, however, I did it for all - cluster, reverse proxy and client certificates. |
I have followed this tutorial to the letter several times but cannot get Https to work when deployed to Service Fabric.
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-dotnet-app-enable-https-endpoint
Everything works in local service Fabric, the application deploys and looks healthy but when browsing responds immediately with ERR_CONNECTION_CLOSED
When I try in Powershell Invoke-WebRequest I get
The underlying connection was closed: An unexpected error occurred on a send
The text was updated successfully, but these errors were encountered: