I installed the SLL certificate on my Windows Service using ACME. I can see the Binding and it looks OK but the domain is not secured…
My domain is: findyourtechstg.northeurope.cloudapp.azure.com/#/main/charts
I installed the SLL certificate on my Windows Service using ACME. I can see the Binding and it looks OK but the domain is not secured…
My domain is: findyourtechstg.northeurope.cloudapp.azure.com/#/main/charts
Hi @MaayanD
checking your domain you have created a new certificate - https://check-your-website.server-daten.de/?q=findyourtechstg.northeurope.cloudapp.azure.com#ct-logs
Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
---|---|---|---|---|---|
Let's Encrypt Authority X3 | 2019-11-07 | 2020-02-05 | findyourtechstg.northeurope.cloudapp.azure.com - 1 entries | duplicate nr. 1 |
But your https is invisible, only timeouts. Your http / port 80 works.
Is there a blocking firewall?
Works https internal?
curl https://findyourtechstg.northeurope.cloudapp.azure.com/
in a DosBox from that machine?
Thank you. No, it is not accessible with Curl as well. I get Timeout
Check the local firewall and ensure there is a listener on port 443.
Perhaps share a screenshot of your bindings.
That looks good. No specific ip address selected (sometimes a problem), SNI is required, no typo visible.
If the website is started, it should work internal (DosBox + curl + https://findyourtechstg.northeurope.cloudapp.azure.com
).
If it doesn’t work internal, there is a blocking instance you have to find.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.