Wordpress Multi-Site - Redirection Error

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: https://*.dbcleanse.nz

I ran this command: sudo certbot -v

It produced this output: Not suggesting name “*.dbcleanse.nz”
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/certbot/util.py”, line 310, in get_filtered_names
filtered_names.add(enforce_le_validity(name))
File “/usr/lib/python3/dist-packages/certbot/util.py”, line 526, in enforce_le_validity
“Valid characters are A-Z, a-z, 0-9, ., and -.”.format(domain))
certbot.errors.ConfigurationError: *.dbcleanse.nz contains an invalid character. Valid characters are A-Z, a-z, 0-9, ., and -.

My web server is (include version): nginx version 1.15.8

The operating system my web server runs on is (include version):Ubuntu 18.04.3
My hosting provider, if applicable, is: Digital Ocean

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 - digital ocean droplet - I log on via terminal

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

1 Like

Wildcard cert requests require DNS authentication which in turn has additional requirements.
Please read through the different challenge types: https://letsencrypt.org/docs/challenge-types/

1 Like

Hi Rudy

Thanks for your response - I can’t see a solution in those challenges. The problem I am having is that the root domain re-directs to another site on my server. The SSL is working on the sub-domains and if I remove the Wildcard on the server name then the root domain is fine also…

This is my hosts file … can you see anything obviously wrong?

server {
listen 80;
listen [::]:80;

server_name *.dbcleanse.nz;

listen 443 ssl http2;
listen [::]:443 ssl http2;
ssl_certificate /etc/letsencrypt/live/dbcleanse.nz-0001/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/dbcleanse.nz-0001/privkey.pem;

access_log /home/matt/dbcleanse.nz/logs/access.log;
error_log /home/matt/dbcleanse.nz/logs/error.log;

root /home/matt/dbcleanse.nz/public/;
index index.php;


location / {
    try_files $uri $uri/ /index.php?$args;
}

location ~ \.php$ {
    try_files $uri =404;
    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    fastcgi_pass unix:/run/php/php7.2-fpm.sock;
    fastcgi_index index.php;
    include fastcgi_params;
}

}

1 Like

Hi,

I’m not sure about the certbot warning output (Maybe due to the fact it’s required to use DNS challenge and you used http based), but your root domain not working problem looks like a easy solve.

Since you already got a certificate on your wildcard domains with DNS authorization, you should add the root domain into the same certificate with DNS challenge.
For example:
sudo certbot -d *.dbcleanse.nz -d dbcleanse.nz (instead of only a wildcard or only root, since those would use a single txt record)

It looks like to me now your root site have a security error (mismatch), because when I visited the website on root domain, I see the wildcard certificate (that doesn’t include root domain).

Is this the issue you are encountering?

Or do you want to add both your wildcard domain and root domain into a single server host?

Thank you

2 Likes

Hi Steven

Yes the mismatch is the error that I’m encountering… dbcleanse.nz (root) redirects to a2ztools.co.nz (or does not load)

The sub domain (thinknew.dbcleanse.nz) works fine.

Do you know how I can fix the mis match issue ?

Is this what you mean when you say add re-issue the certbot command ?

Many thanks for your guidance

Matt

1 Like

Thanks Steven

sudo certbot -d *.dbcleanse.nz -d dbcleanse.nz

That did the trick

Really appreciate your support

Matt

2 Likes

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