Authorization timed out (new certificate creation)

[Flheart]

Hello,

I cannot generate certificates using Let’s Encrypt executable in interactive mode.
I get an authorization timed out error. I enabled the --verbose switch to launch the tool but I’m not getting further details to help me troubelshoot in the right direction.
Could you please help me figure out the underlying issue preventing me from generating the required certificates ?

Kind regards,

My domain is: kattoumrafik.com

I ran this command: Used wacs.exe with options N and then 4

It produced this output: Authorization timed out / Create certificate failed: authorization failed

My web server is (include version): IIS 8.5

The operating system my web server runs on is (include version): Windows 2012R2

My hosting provider, if applicable, is: n/a

I can login to a root shell on my machine (yes or no, or I don’t know): it’s a Windows machine

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

[JuergenAuer]

Hi @Flheart

@Flheart

My domain is: kattoumrafik.com

your port 80 doesn't answer ( https://check-your-website.server-daten.de/?q=kattoumrafik.com ):

Domainname	Http-Status	redirect	Sec.	G
• http://kattoumrafik.com/
83.142.90.188	-14		10.027	T
Timeout - The operation has timed out
• https://kattoumrafik.com/
83.142.90.188	301	https://kattoumrafik.com/owa/	1.383	B
• https://kattoumrafik.com/owa/	302	https://kattoumrafik.com/owa/auth/logon.aspx?url=https%3A%2F%2Fkattoumrafik.com%2Fowa%2F&reason=0	0.246	B
• https://kattoumrafik.com/owa/auth/logon.aspx?url=https%3A%2F%2Fkattoumrafik.com%2Fowa%2F&reason=0	200		0.303	B
• kattoumrafik.com
83.142.90.188	-14		10.023	T
Timeout - The operation has timed out
Visible Content:

You need an open port 80 to use http-01 - validation. Only port 443 is visible.

[Flheart]

Hello Juergen,

After allowing traffic on port 80 through our perimeter firewall, and configuring redirects from http to https, plus a few other setup steps, I managed to get my new bindings working Ok in IIS, and all the relevant Exchange services are now responding to external requests with the right certificate !
Thank you for your quick, but efficient help.

Could you also please confirm that installing the same certificate on other role servers in my Exchange 2k13 infrastructure requires that I should do within the next 10 minutes following the cert issuance ?

Many thanks again.

Best regards.