"invalid host in redirect target" - Can't find the error

Help
1

My domain is: cartan.hopto.org

I ran this command:certbot certonly --webroot -w /usr/local/www/nexcloud -d cartan.hopto.org

It produced this output:

Invalid host in redirect target "cartan.hopto.org.well-known".
Check webserver config for missing '/' in redirect target.

My web server is (include version): NextCloud 18 on Apache2.4

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

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

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

Question: I understand the issue is with this redirect such that it sees "cartan.hopto.org.well-known" instead of "Nextcloud", but I can't find where this redirect is configured in ?? What/where do I need to change somehting (Apologies for a probably very basic question from a newbie) ?

I ran cartan.hopto.org - Make your website better - DNS, redirects, mixed content, certificates and it confirms "redirect to not existing domain"

Thanks in advance for any help !
Tanguy

2

Probably in the Apache configuration file containing the HTTP VirtualHost section. Another posibility would be a .htaccess file in the document root of the virtualhost.

3

Hi @carrabta

see your check:

Domainname Http-Status redirect Sec. G
• http://cartan.hopto.org/ 81.157.57.194 301 https://cartan.hopto.org Html is minified: 100,00 % 0.060 A

There is already the "missing /". That's not a problem because that works. But with a subfolder, it's the "missing /".

So your first redirect http -> https is wrong.

It's not only the redirect http + /.well-known/acme-challenge -> https + /.well-known/acme-challenge.

4

Excellent, guys - I think I found it !
So it was in the definition of the virtual host (attached screenshot).

capture virtual host
capture virtual host822×350 81.8 KB
in /usr/local/etc/apache24/Includes.
I have added the ‘/’ at the end of “https://cartan.hopto.org**/**” under the virtual host *.80.

I could update the certificate, that worked. I’m still struggling with access though, but probably another cause, as you seem to point out, Juergen. Although it was working fine before, so not sure where to look, now…

Thanks again.
Tanguy