# Unauthorized error when renewing certificate

**URL:** <https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675>\
**Category:** Help\
**Created:** [April 28, 2021, 9:46pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675 "2021-04-28T21:46:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![djgundrum](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/djgundrum/32/49229_2.png) [@djgundrum](https://community.letsencrypt.org/u/djgundrum)\
**Post date:** [April 28, 2021, 9:46pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/1 "2021-04-28T21:46:34Z")

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

I ran this command: certbot --nginx -d [storylinq.com](http://storylinq.com) -d [www.storylinq.com](http://www.storylinq.com)

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Plugins selected: Authenticator nginx, Installer nginx  
Cert is due for renewal, auto-renewing...  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for [storylinq.com](http://storylinq.com)  
http-01 challenge for [www.storylinq.com](http://www.storylinq.com)  
nginx: [warn] conflicting server name "[storylinq.com](http://storylinq.com)" on 0.0.0.0:80, ignored  
nginx: [warn] conflicting server name "[www.storylinq.com](http://www.storylinq.com)" on 0.0.0.0:80, ignored  
Waiting for verification...  
Cleaning up challenges  
nginx: [warn] conflicting server name "[storylinq.com](http://storylinq.com)" on 0.0.0.0:80, ignored  
nginx: [warn] conflicting server name "[www.storylinq.com](http://www.storylinq.com)" on 0.0.0.0:80, ignored  
Failed authorization procedure. [www.storylinq.com](http://www.storylinq.com) (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [https://www.storylinq.com/.well-known/acme-challenge/sN1hrbxAdQvBIZk9rdLDPmzs-qYQ5pVAh1qLwo4Ycm4](https://www.storylinq.com/.well-known/acme-challenge/sN1hrbxAdQvBIZk9rdLDPmzs-qYQ5pVAh1qLwo4Ycm4) [45.82.72.223]: "\n\<html lang="en"\>\n\n\<meta charset="utf-8"\>\nError\n\n\n

```
Cannot GET /.well-known/",[storylinq.com](http://storylinq.com)(http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from[https://storylinq.com/.well-known/acme-challenge/DpTcZqyOwJ0o3YDu3JW5yEP\_JI7L0Umy4xfuiHieT6Q](https://storylinq.com/.well-known/acme-challenge/DpTcZqyOwJ0o3YDu3JW5yEP_JI7L0Umy4xfuiHieT6Q)[45.82.72.223]: "\n<html lang="en">\n\n<meta charset="utf-8">\nError\n\n\n
```
Cannot GET /.well-known/"

IMPORTANT NOTES:
```
```

- The following errors were reported by the server:

My web server is (include version): Nginx

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

My hosting provider, if applicable, is: Hostinger

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

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

---

<div class="post-metadata">

**Author:** ![djgundrum](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/djgundrum/32/49229_2.png) [@djgundrum](https://community.letsencrypt.org/u/djgundrum)\
**Post date:** [April 28, 2021, 9:52pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/2 "2021-04-28T21:52:37Z")

</div>

Hey I'm really sorry I saw things that were similar to my case but nothing seemed to work so I went ahead and opened one for myself. I hope this is enough to understand.

Some more things that may be helpful are that I am running nginx to proxy to a port where I have my nodejs application running with pm2.

I can paste anything needed for this, I am just confused how to fix

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [April 28, 2021, 10:22pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/3 "2021-04-28T22:22:52Z")

</div>

Hi @djgundrum

> [@djgundrum](#):
>
> nginx: [warn] conflicting server name "[storylinq.com](http://storylinq.com)" on 0.0.0.0:80, ignored  
> nginx: [warn] conflicting server name "[www.storylinq.com](http://www.storylinq.com)" on 0.0.0.0:80, ignored

there is your problem you have to fix.

Duplicated combinations of port and domain names -\> fatal buggy configuration.

Fix that.

---

<div class="post-metadata">

**Author:** ![djgundrum](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/djgundrum/32/49229_2.png) [@djgundrum](https://community.letsencrypt.org/u/djgundrum)\
**Post date:** [April 28, 2021, 10:30pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/4 "2021-04-28T22:30:52Z")

</div>

what would you say is the best way to go about fixing that? Thank you for the quick response by the way, it is very appreciated \<3

---

<div class="post-metadata">

**Author:** ![djgundrum](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/djgundrum/32/49229_2.png) [@djgundrum](https://community.letsencrypt.org/u/djgundrum)\
**Post date:** [April 28, 2021, 10:47pm UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/5 "2021-04-28T22:47:53Z")

</div>

Thanks for everything, I checked it out and I got it working again. Very appreciated.

---

<div class="post-metadata">

**Author:** ![tlrenkensebastian](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tlrenkensebastian/32/47494_2.png) [@tlrenkensebastian](https://community.letsencrypt.org/u/tlrenkensebastian)\
**Post date:** [April 29, 2021, 12:32am UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/6 "2021-04-29T00:32:27Z")

</div>

Hey, glad to see you were able to sort things out. Also, I'd like to say thank you for confirming that you'd searched the forum posts first before creating your own post because it's a great way of beginning any kind of community forum troubleshooting. Welcome to the community!

---

<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:** [May 29, 2021, 12:33am UTC](https://community.letsencrypt.org/t/unauthorized-error-when-renewing-certificate/150675/7 "2021-05-29T00:33:23Z")

</div>

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