Hi, Thank for help. I already studied the issue and tried to fix. But I ll need help. Seems like something simple. Yet I havent found the solution and my issue didnt seem to match other topics.
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.
My web server is (include version): I have just taken this VPS…in the Services I didnt see apache or nignx… Do I need to find this from them ?
The operating system my web server runs on is (include version): Centos 7 OS
My hosting provider, if applicable, is:goolhost
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):not using control panel right now.
Thanks for immediate reply. Appreciate.
Now when I tried to run this …it was conficting with httpd as that was on port 80 …So I disabled httpd from running services. Now that should have some thing to do with no running webserver ? I dont think there is a firewall but Let me check with the VPS provider. Thanks.
Ok When I start the httpd which is my webserver Apache.
systemctl start httpd
[root@neurotech ~]# certbot certonly --preferred-challenges http-01 -d neurotechdesigns.ddns.net
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 1
Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for neurotechdesigns.ddns.net
Cleaning up challenges
Problem binding to port 80: Could not bind to IPv4 or IPv6.
I am thankful for your help. I tried the option 2 …yet the same error as above.
I checked the status of httpd and this line intrigues me.httpd: Could not reliably determine the server’s fully qualified domain name,…message
root@neurotech ~]# systemctl status httpd
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2019-01-18 15:23:00 EST; 1min 52s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 7995 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
Main PID: 10749 (httpd)
Status: “Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec”
CGroup: /system.slice/httpd.service
├─10749 /usr/sbin/httpd -DFOREGROUND
└─10750 /usr/sbin/httpd -DFOREGROUND
Jan 18 15:23:00 neurotech systemd[1]: Starting The Apache HTTP Server…
Jan 18 15:23:00 neurotech httpd[10749]: AH00558: httpd: Could not reliably determine the server’s fully qualified domain name,…message
Jan 18 15:23:00 neurotech systemd[1]: Started The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.
Any idea why it saying that. And when I ssh from my computer to login to the hostname it works … So this is visible I think.
ssh root@neurotechdesigns.ddns.net works.
Can you suggest something. See I got this free ip from noip to map to the VPS IP. Shall I check with them. Does it take some time to become active and visible globally. Its been 5-6 hrs or less since I created this with them.
Regards. Just cant understand.I have used the same hostname ie neurotechdesigns.ddns.net and installed the certificates in September 2018. Since VPS deactivated because we didnt need it. And today again we have reactivated the VPS. I am trying to provide the neccessary information. Thanks for patience.
I don't know if this service blocks port 80 generally or if it is a special problem of your domain name.
You can use dns-01 - validation. Then you don't need an open port 80. But then you have to create a dns txt entry with a special value. And you have to do that manual if your nf1.no-ip.com` doesn't have a DNS API.