Unable to browse to https after installing LetsEncrypt


#1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: qanfse.infosys-ife.com

I ran this command: (Actually, we ran a PowerShell script)

It produced this output: (lots of lines)

My web server is (include version): (not sure how to answer this question)

The operating system my web server runs on is (include version): Microsoft Hyper-V Server 2016

My hosting provider, if applicable, is: AWS

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

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

I and my co-worker have just installed a LetsEncrypt certificate, but we are unable to browse to the web site either as https://localhost or as https://qanfse.infosys-ife.com… It times out. We are still able to browse to its http version, though.

We followed instruction from this video: https://www.youtube.com/watch?v=Z3jd8NOOY2o&feature=youtu.be

We are not really sure what should we do to have it working.
Can someone, please, point us in the right direction?

Thanks in advance.


#2

Hi @oracy,

All of these details are really important. That’s why we ask about them. :slight_smile: For example, we want to know whether you are using IIS, nginx, Apache, lighttpd, or something else, what PowerShell script you used, whether it said it was successful or unsuccessful, whether it said that it created an HTTPS service or that you still have to do that yourself, etc.

Please find these answers for us so that we can understand more about what you did.

For example, one possibility is that the script simply obtained the certificate but didn’t configure HTTPS in your web server. This is not an unusual behavior because many people regard installing certificates as a separate operation from obtaining them. Another possibility is that you have a firewall blocking access to port 443. If we saw the complete output of the script, we might have more information about likely explanations.


#3

Hi, I understand that.
I thank you anyway, as you pointed me in the right direction: Port 403 was blocked indeed.

Thank you very much again.


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.