It will not complete says "NXDOMAIN looking up A for api.kriptokng.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for api.kriptokng.com - check that "

Help
1

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: kriptokyng.com

I ran this command:

It produced this output:NXDOMAIN looking up A for api.kriptokng.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for api.kriptokng.com - check that

My web server is (include version):

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

My hosting provider, if applicable, is:namescheap.com

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

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

3

Looks like you mis-typed your domain name when you requested the certificate. Ends in kng.com not kyng.com

5

server {
server_name api.kriptokng.com;

location / {
    proxy_pass http://localhost:4000;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
}

}

server {
server_name stratum.kriptokng.com;

location / {
    add_header 'Access-Control-Allow-Origin' '*' always;
    add_header 'Access-Control-Allow-Methods' 'GET,HEAD,OPTIONS' always;
    add_header 'Access-Control-Allow-Headers' '*' always;

    default_type application/json;
    return 200 '{"status":"ok","message":"Stratum is alive"}';
}

}

server {
server_name kriptokng.com www.kriptokng.com;

location / {
    proxy_pass http://localhost:3000;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
location /notify {
    proxy_pass http://127.0.0.1:4000/notifications;  # The URL of your WebSocket server
   	proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
	proxy_set_header X-NginX-Proxy true;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_redirect off;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    }

}

server {
if ($host = www.kriptokng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

if ($host = kriptokng.com) {
    return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name kriptokng.com www.kriptokng.com;
return 404; # managed by Certbot

}

server {
if ($host = api.kriptokng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name api.kriptokng.com;
return 404; # managed by Certbot

}

server {
if ($host = stratum.kriptokng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name stratum.kriptokng.com;
return 404; # managed by Certbot

}

6

Is your domain kriptokng.com or kriptokyng.com? Your OP says the second, but all the server config blocks you've posted for some reason say the first. But kryptokng.com doesn't appear to exist.

7

Good catch DANB35, that was the issue.

8

Not my catch; @MikeMcQ caught it in his post yesterday.

9

OK got it to cert, but my pool is not connecting with api.kriptokng.com:443

11

server {
server_name api.kriptokyng.com;

location / {
    proxy_pass http://localhost:4000;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    
}
    
	listen 443 ssl; # managed by Certbot
	ssl_certificate /etc/letsencrypt/live/kriptokyng.com-0005/fullchain.pem; # managed by Certbot
	ssl_certificate_key /etc/letsencrypt/live/kriptokyng.com-0005/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 {
server_name kriptokyng.com www.kriptokyng.com;

location / {
    proxy_pass http://127.0.0.1:3000;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
location /notify {
    proxy_pass http://127.0.0.1:4000/notifications;  # The URL of your WebSocket server
   	proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
	proxy_set_header X-NginX-Proxy true;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_redirect off;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}
listen 443 ssl; # managed by Certbot
	ssl_certificate /etc/letsencrypt/live/kriptokyng.com-0005/fullchain.pem; # managed by Certbot
	ssl_certificate_key /etc/letsencrypt/live/kriptokyng.com-0005/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 {
server_name stratum.kriptokyng.com;

location / {
    add_header 'Access-Control-Allow-Origin' '*' always;
    add_header 'Access-Control-Allow-Methods' 'GET,HEAD,OPTIONS' always;
    add_header 'Access-Control-Allow-Headers' '*' always;

    default_type application/json;
    return 200 '{"status":"ok","message":"Stratum is alive"}';
}

listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/kriptokyng.com-0005/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/kriptokyng.com-0005/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 {
if ($host = www.kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

if ($host = kriptokyng.com) {
    return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name kriptokyng.com www.kriptokyng.com;
return 404; # managed by Certbot

}

server {
if ($host = api.kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name api.kriptokyng.com;
return 404; # managed by Certbot

}

server {
if ($host = stratum.kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name stratum.kriptokyng.com;
return 404; # managed by Certbot

}

server {
if ($host = kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

server_name kriptokyng.com www.kriptokyng.com;
listen 80;
return 404; # managed by Certbot

}server {
if ($host = api.kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

server_name api.kriptokyng.com;
listen 80;
return 404; # managed by Certbot

}

server {
if ($host = stratum.kriptokyng.com) {
return 301 https://$host$request_uri;
} # managed by Certbot

server_name stratum.kriptokyng.com;
listen 80;
return 404; # managed by Certbot

}

12

And it won't. That is not your domain name.

Yours is api.kriptokyng.com. The name api.kriptokng.com has not been purchased by anyone.