# Renewing certificate behind https

**URL:** <https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157>\
**Category:** Help\
**Created:** [September 13, 2017, 2:37pm UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157 "2017-09-13T14:37:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![doludizgin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/doludizgin/32/19372_2.png) [@doludizgin](https://community.letsencrypt.org/u/doludizgin)\
**Post date:** [September 13, 2017, 2:37pm UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/1 "2017-09-13T14:37:47Z")

</div>

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](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: [hyperimes.com](http://hyperimes.com)

I ran this command: usr/bin/certbot renew

It produced this output: Attempting to renew cert ([hyperimes.com](http://hyperimes.com)) from /etc/letsencrypt/renewal/hyperimes.com.conf produced an unexpected error: Failed authorization procedure. [hyperimes.com](http://hyperimes.com) (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://hyperimes.com/.well-known/acme-challenge/blHjAPfq7M2ecnfk1F7jR3WThcYPt-GiqIPCTZLpN7s:](http://hyperimes.com/.well-known/acme-challenge/blHjAPfq7M2ecnfk1F7jR3WThcYPt-GiqIPCTZLpN7s:) Timeout. Skipping.

My web server is (include version):

The operating system my web server runs on is (include version): Ubuntu 16.04

My hosting provider, if applicable, is:

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

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

[https://hyperimes.com/.well-known/acme-challenge/test.txt](https://hyperimes.com/.well-known/acme-challenge/test.txt) is reachable. But still having problems with renewing the certificate.

I am running nginx with http to https rewrite, is this the problem ?

---

<div class="post-metadata">

**Author:** ![jared.m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jared.m/32/17871_2.png) [@jared.m](https://community.letsencrypt.org/u/jared.m)\
**Post date:** [September 13, 2017, 4:32pm UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/2 "2017-09-13T16:32:32Z")

</div>

The rewrite shouldn’t be an issue, as Let’s Encrypt follows up to several redirects. Could you post the relevant vhost configuration and Let’s Encrypt log files? At a glance I don’t see any reason this wouldn’t be working.

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [September 13, 2017, 4:46pm UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/3 "2017-09-13T16:46:55Z")

</div>

Hi @doludizgin,

I can’t reach your http site too:

```
$ curl -IkL http://hyperimes.com
curl: (7) Failed to connect to hyperimes.com port 80: Connection timed out

```

but I can reach your https site:

```
$ curl -IL https://hyperimes.com
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Wed, 13 Sep 2017 16:41:23 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Sat, 08 Jul 2017 10:36:58 GMT
Connection: keep-alive
ETag: "5960b5ca-264"
Strict-Transport-Security: max-age=63072000; includeSubdomains
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Accept-Ranges: bytes

```

So seems a firewall blocking port 80 or something not properly configured in your nginx conf 🙂

Cheers,  
sahsanu

---

<div class="post-metadata">

**Author:** ![gotham](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/gotham/32/16320_2.png) [@gotham](https://community.letsencrypt.org/u/gotham)\
**Post date:** [September 14, 2017, 5:28am UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/4 "2017-09-14T05:28:00Z")

</div>

@doludizgin , If you are using proper rewrite rule , when we hit [http://hyperimes.com](http://hyperimes.com) it should redirect to [https://hyperimes.com](https://hyperimes.com) . can you post your config here.

or

make site available in http and https by removing rewrite rule .so that it can reach your site .

---

<div class="post-metadata">

**Author:** ![doludizgin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/doludizgin/32/19372_2.png) [@doludizgin](https://community.letsencrypt.org/u/doludizgin)\
**Post date:** [September 14, 2017, 7:48am UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/5 "2017-09-14T07:48:25Z")

</div>

Oh stupid me, blocked port 80…

it worked.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [October 14, 2017, 7:48am UTC](https://community.letsencrypt.org/t/renewing-certificate-behind-https/42157/6 "2017-10-14T07:48:33Z")

</div>

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