I am working in a new Ubunut VM with a NodeJS and Express server, there is no Apache or NGINX but someone created the VM for me to deploy this application.
The is a Google analytics script on the index.html, could that be the cause?
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
My web server is (include version):
The operating system my web server runs on is (include version):
Ubuntu 16
My hosting provider, if applicable, is:
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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
Looks like that doesn’t work. Did you stop your webserver manual before starting Certbot?
Yes I did
Is there another instance that blocks?
I'm not certain because the machine I am working on was setup by the person responsible for the cpanel.
Where did you run that certbot?
I ran the certbot in the root folder of the NodeJS's server source files.
And: There is a cPanel-certificate:
Could this be the possible cause?
I do not have full access to all the ENV setup, I do have a root user in the Ubuntu machine.
I am rather clueless what is happening now.
There is this on the output from https://check-your-website.server-daten.de/?q=newzroomafrika.tv
Could it be the http-equiv?
Or something from the cpanel side?
Thank you
Here is the output
Maybe I should try making certain that I have stopped the server before creating the certificate.
I will have to do it when I am at the office because I am restricted to using the IP from there,
Okay thank you @JuergenAuer.
I will do that, I hope you will be available in case I face some issues.
But in any case thank you for your time and assistance, I appreciate it.
I don't know. Do you run Certbot on the same server where the Express runs?
If not, that can't work.
Perhaps it's easier if you check the documentation of that Express. So you can use that Express directly to create a Letsencrypt certificate, so you don't need to stop it.
