My domain is:sherlockmeet.expertsystem.co.in
I ran this command: Let's Debug
It produced this output: got all ok
Ubuntu 20.04.2 LTS
My hosting provider, if applicable, is: local server
I can login to a root shell on my machine (yes or no, or I don't know): yes
Could you please elaborate a little bit (or perferably: a lot) more about why you "cant able get ssl"? Which command did you run to get the SSL for the new subdomain? And what output did that give you?
cmd : sudo /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh
output
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for sherlockmeet.expertsystem.co.in
Using the webroot path /usr/share/jitsi-meet for all unmatched domains.
Waiting for verification...
Challenge failed for domain sherlockmeet.expertsystem.co.in
http-01 challenge for sherlockmeet.expertsystem.co.in
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: sherlockmeet.expertsystem.co.in
Type: connection
Detail: During secondary validation: Fetching
http://sherlockmeet.expertsystem.co.in/.well-known/acme-challenge/--SsEmXibaqgKxUu-qs3juyKGfgd3b-MsaICJ_95lQQ:
Timeout after connect (your server may be slow or overloaded)
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.
please help me out i am really stuck at this point
Please be patient, this Community is mainly run by volunteers and most probably have regular day jobs (I do at least..)
i really appreciates it @Osiris .
This seems a bit telling:
How busy is your server?
Please show the output of:
sudo top
It now fails:
Let's Debug (letsdebug.net)
i was working around please wiat i give you output
OK that explains the failures 
now please check status is ok
I'm not familiar with this script, but it seems to be using this --webroot:
We can place a test file in that location to verify if nginx is properly configured to serve from there with:
mkdir /usr/share/jitsi-meet/.well-known
mkdir /usr/share/jitsi-meet/.well-known/acme-challenge
echo "test file 1234" > /usr/share/jitsi-meet/.well-known/acme-challenge/Test-File-1234
and then check for file access with
http://sherlockmeet.expertsystem.co.in/.well-known/acme-challenge/Test-File-1234
If that file is not accessible from the Internet, then the challenge path doesn't match.
I have to step away for a few hours.
Maybe someone else can step in OR I can continue working with you when I return.
ok let me do that . thanks for response
sudo echo "test file 1234" > /usr/share/jitsi-meet/.well-known/acme-challenge/Test-File-1234
-bash: /usr/share/jitsi-meet/.well-known/acme-challenge/Test-File-1234: Permission denied
sherlock@sherlockmeet:~$ sudo echo "Test-File-1234" > /usr/share/jitsi-meet/.well-known/acme-challenge/Test-File-1234
-bash: /usr/share/jitsi-meet/.well-known/acme-challenge/Test-File-1234: Permission denied
i am totally lost here guide me more please
Could you please share the file /etc/nginx/sites-available/sherlockmeet.expertsystem.co.in.conf ?
server_names_hash_bucket_size 64;
types {
# nginx's default mime.types doesn't include a mapping for wasm
application/wasm wasm;
}
server {
listen 80;
listen [::]:80;
server_name sherlockmeet.expertsystem.co.in;
location ^~ /.well-known/acme-challenge/ {
default_type "text/plain";
root /usr/share/jitsi-meet;
}
location = /.well-known/acme-challenge/ {
return 404;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name sherlockmeet.expertsystem.co.in;
# Mozilla Guideline v5.4, nginx 1.17.7, OpenSSL 1.1.1d, intermediate configuration
ssl_protocols TLSv1.2 TLSv1.3;
Interesting.. So the webroot should be OK looking at that section, but somehow it doesn't actually work?
Could you paste the entire output of sudo nginx -T? It shows all the configuration parameters currently actually in use. Please put three backticks (```) on a separate line above and below the output. Like this:
```
output
```