Unauthorized error when renewing certificate

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), 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

I ran this command: certbot --nginx -d storylinq.com -d 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-01 challenge for www.storylinq.com
nginx: [warn] conflicting server name "storylinq.com" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "www.storylinq.com" on 0.0.0.0:80, ignored
Waiting for verification...
Cleaning up challenges
nginx: [warn] conflicting server name "storylinq.com" on 0.0.0.0:80, ignored
nginx: [warn] conflicting server name "www.storylinq.com" on 0.0.0.0:80, ignored
Failed authorization procedure. 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 [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-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from 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:

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

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

1 Like

Hi @djgundrum

there is your problem you have to fix.

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

Fix that.

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

1 Like

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

1 Like

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!

2 Likes

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