Invalid empty hostname in redirect target

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:

vegabolgen.no

I ran this command:

certbot-auto renew

It produced this output:

The following errors were reported by the server:

Domain: www.vegabolgen.no
Type: connection
Detail: Fetching
https:/www.vegabolgen.no/.well-known/acme-challenge/_6_ZhihTEUh2ch-irmii8jQqjPMmWRvegTOnn_UsYw8:
Invalid empty hostname in redirect target

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version):

nginx 1.18.0

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

CentOS 8

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

1.9.0

I am getting this error trying to update my certificate but I do not understand the error message, as far as I can see, everything is as it should..?

BTJ

2 Likes
$ curl -X GET -I www.vegabolgen.no/.well-known/acme-challenge/test
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 26 Nov 2020 09:32:22 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https:/www.vegabolgen.no/.well-known/acme-challenge/test

See that Location line? The URL should say https://, but you only have one forward slash.

Take a look at your nginx configuration, it's probably a mistake in how you configured the HTTPS redirect.

3 Likes

Hmmm... Seriously.... I looked at the link many times, how did I not catch that....
Thx... :slight_smile:

3 Likes

Funny enough :/ translates (is displayed as) to: :confused:
So there is a sad and confused face in your URL !

3 Likes

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