Subdomain failed during installation

Help
21

Thanks I will try it now and let you know .

1 Like
22

sorry, it did not worked

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

    root /var/www/vmeet.ca/html;
    index index.html index.htm;

    server_name vmeet.ca  www.vmeet.ca;

    if ($scheme=='http') {
    return 301 https://$host$request_uri;
    }
    location / {
            try_files $uri $uri/ =404;
    }
1 Like
23

Then try it as two separate server sections (one for HTTP another for HTTPS):

server {
    listen 80;
    listen [::]:80;
    root /var/www/vmeet.biz/html;
    index index.html index.htm;
    server_name vmeet.biz  www.vmeet.biz;
    return 301 https://$host$request_uri;
}#server

server {
    listen [::]:443 ssl; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    root /var/www/vmeet.biz/html;
    index index.html index.htm;
    server_name vmeet.biz  www.vmeet.biz;
    location / {
            try_files $uri $uri/ =404;
    }#location
    ssl_certificate /etc/letsencrypt/live/www.vmeet.ca/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/www.vmeet.ca/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}#server
1 Like
24

did follow with your suggestion changing the config inside the server blocks but no changes from the browser end, I maintain the domain with .ca while your suggestion is on the .biz

1 Like
25

Dude, I just modified what you posted.
Feel free to adjust it accordingly.

1 Like
26

is that good or bad?

27

I don’t understand the question…

28

sorry, just to responding to your last comment, either way, there is no changes from the browser end still not secured?
In case you need to know I restart the Nginx and purge all history from the web site browsing

29

I don’t know your config.
You said you had a problem and showed some code.
I asked you to include some code but that failed to fix it.
So I modified the code you showed to separate the HTTP form the HTTPS in an attempt to fix your problem.

If that is NOT the code with the problem, then why did you post it?

#1: Your problem now has nothing to do with LE nor the certificate - it is entirely an NGINX coding problem
#2: If you can’t figure how to use the example provided, then you probably shouldn’t be coding in the first place.

1 Like
30

I am not sure if it is the code or not, but in any case the Nginx is not listening the server block command, the LE certificate is registered but Nginx is not doing what it supposed to do, one other question from this:
I noticed the certificate is www.vmeet.ca/fullchain.pem
will that the same on all other domains? including .biz?

31

You can see which certs you have and which domains they cover with:
certbot certificates

1 Like
32

root@conference:/home/michael# cerbot certificates

Command ‘cerbot’ not found, did you mean:

command ‘certbot’ from deb certbot

Try: apt install

Not sure how this is happening…

33

Are you using two systems?
Your initial post said you had certbot and you claim to have a useable cert.
Please explain.

34

Yes I just installed the cert today and you see the certificate showed as it stated on the config file
I used the certbot site instruction installed the cert
and follow its instruction on certbot -i nginx -d domain -d www.domain etc

35

just check my response to you , there were typo on my part for the certbot but no “t”

1 Like
36

Yes, I see the typo now too.
Happens when I type too fast - lol
[went back and fixed it]

1 Like
37

The cert name listed with domains included , does that conflict with what we are trying to do?

Certificate Name: vmeet.ca
Domains: vmeet.ca vmeet.biz
Expiry Date: 2020-09-11 19:48:11+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/vmeet.ca/fullchain.pem
Private Key Path: /etc/letsencrypt/live/vmeet.ca/privkey.pem
Certificate Name: www.vmeet.ca
Domains: www.vmeet.ca www.vmeet.biz
Expiry Date: 2020-09-11 20:26:37+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/www.vmeet.ca/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.vmeet.ca/privkey.pem

38

Oh, that’s terrible.
The WWW’s are in a cert by themselves.
And the names are criss-crossed…

It should be:
cert 1:
Domains: vmeet.ca www.vmeet.ca
cert 2:
Domains: vmeet.biz www.vmeet.biz

or just one cert with all four in it:
Domains: vmeet.ca www.vmeet.ca vmeet.biz www.vmeet.biz

1 Like
39

OK, how to fix that do I need to reinstall the cert? Can I do a roll back on certbot rollback nginx -d vmeet.ca -d vmeet.biz -d www.vmeet.ca -d www.vmeet.biz and reinstall as you suggested?

40

You need to get a new cert (or two).
Then use them as needed.