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. crt.sh | 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:vizagdomain.com
I ran this command: ran wacs.exe in admin mode and creating the certificate
It produced this output: No valid IP addresses found for vizagdomain.com
My web server is (include version): IIS windows 10 version
The operating system my web server runs on is (include version): windows 10 pro
My hosting provider, if applicable, is:
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):
That's not a worldwide unique, public visible ip address. That's a private ip address.
A public visible ip address is required if you want to use http validation.
PS: See the comments:
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check Private network - Wikipedia to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses