Invalid response from / well-known/acme-challenge

Please note I have used to check and it all came ok.

My domain is:

I ran this command: ./certbot-auto certonly --standalone --debug -d

It produced this output:

http-01 challenge for
Waiting for verification…
Challenge failed for domain
http-01 challenge for
Cleaning up challenges
Exiting abnormally:
Traceback (most recent call last):
File “/opt/”, line 11, in
File “/opt/”, line 15, in main
return internal_main.main(cli_args)
File “/opt/”, line 1357, in main
return config.func(config, plugins)
File “/opt/”, line 1237, in certonly
lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
File “/opt/”, line 121, in _get_and_save_cert
lineage = le_client.obtain_and_enroll_certificate(domains, certname)
File “/opt/”, line 418, in obtain_and_enroll_certificate
cert, chain, key, _ = self.obtain_certificate(domains)
File “/opt/”, line 351, in obtain_certificate
orderr = self._get_order_and_authorizations(, self.config.allow_subset_of_names)
File “/opt/”, line 398, in _get_order_and_authorizations
authzr = self.auth_handler.handle_authorizations(orderr, best_effort)
File “/opt/”, line 91, in handle_authorizations
self._poll_authorizations(authzrs, max_retries, best_effort)
File “/opt/”, line 180, in _poll_authorizations
raise errors.AuthorizationError(‘Some challenges have failed.’)
AuthorizationError: Some challenges have failed.
Please see the logfiles in /var/log/letsencrypt for more details.

 - The following errors were reported by the server:

   Type:   unauthorized
   Detail: Invalid response from
   []: "\n<html><head><meta name=\"viewport\"
   border=\"0\" rows=\"100%,*\" cols=\""

   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): Node Js, Nginx

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

My hosting provider, if applicable, is: My App is hosted on AWS EC2 Linux instance, but the domain is registered using , I am merely using domain forwarding services.

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

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Yes I can, however, I am just using domain forwarding service.

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

At the time of generating certificate I stopped my Nginx service. This is the current Nginx confc;
3000 is where my Node App runs.

For more information on configuration, see:
#   * Official English Documentation:
#   * Official Russian Documentation:

user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    	# Load modular configuration files from the /etc/nginx/conf.d directory.
    	# See
    	# for more information.
   	 include /etc/nginx/conf.d/*.conf;

	listen 80 	default_server;
	listen		[::]:80 default_server;
	server_name	localhost_;
	root		/usr/share/nginx/html;

	# load configuration frils for default server block.
	include	/etc/nginx/default.d/*.confc;
	location / {
		proxy_http_version 1.1;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection 'upgrade';
		proxy_set_header Host $host;
		proxy_cache_bypass $http_upgrade;
	error_page 404 /404.html;
		location = /40x.html{
	error_page 500 502 503 504 /50x.html;
		location = /50x.html{


# Settings for a TLS enabled server.
#	server{
#		listen 		443 ssl http2 default_server;
#		listen 		[::]:443 ssl http2 default_server;
#		server_name	_;
#		root		/usr/share/nginx/html;
#		ssl_certificate	"/etc/pki/nginx/server.crt";
#		ssl_certificate_key "/etc/pki/nginx/private/server.key";
#		ssl_session_cache shared:SSL:1m;
#		ssl_session_timeout  10m;
#		ssl_ciphers PROFILE=SYSTEM;
#		ssl_prefer_server_ciphers on;
# 		load configuration frils for default server block.
#		include	/etc/nginx/default.d/*.confc;
#		error_page 404 /404.html;
#		location = /40x.html{
#		}
#	        error_page 500 502 503 504 /50x.html;
#		location = /50x.html{
#		}
#	}

Hi @scorpion-3

that can’t work, see your check, ~~6 hours old -

Your ip address:

Host Type IP-Address is auth. ∑ Queries ∑ Timeout A Burlington/Massachusetts/United States (US) - PDR No Hostname found yes 1 0
AAAA yes A Burlington/Massachusetts/United States (US) - PDR No Hostname found yes 1 0
AAAA yes

And your check has an explicit warning:

Info: Html-Content with frame found, may be a problem creating a Letsencrypt certificate using http-01 validation

<html><head><meta name="viewport" content="width=device-width,initial-scale=1"></head>
<frameset border="0" rows="100%,*" cols="100%" frameborder="no">
<frame name="TopFrame" scrolling="yes" noresize 
src=""><frame name="BottomFrame" scrolling="no" noresize>

You can’t create a certificate via that

domain forwarding with a frame.

Your A record must point to your, not to that you don’t control.

So is checked, not your 3.7 with your nginx and your Node App.

And you can’t install a certificate on, because you don’t control that webserver.

So a correct certificate would be worthless because you can’t use it.


Oh I get it. so will it work if i try putting in so that at least my Node JS app will have ssl enabled? can I run the below command?
./certbot-auto certonly --standalone --debug -d

As for the domain name, I will have to get the SSL from the hosting provider for that domain I guess.
Let me know if my assumptions are correct.

You can’t create a certificate with an ip address.

Switch the A-record of your domain name or use another domain name with a working dns provider.

Thanks for the quick response, I am actually new to SSL and Domains. Sorry to bother you with silly questions, so if I want my Node JS app to have SSL enabled, I would still need a domain name? If you can point out any article that can help me guide on how to enable SSL for Node JS app on Amazon. That would be helpful.

Follow this tutorial: . You need to setup your DNS like that, instead of using DNS forwarding.

Then after waiting a short while, you can try your original Certbot command again (with your Node.js server stopped).

1 Like

This worked! thanks a ton !

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.