How to issue letsencrypt license

[cyberpersons]

Hi,

How can I get around this issue ?

#################################
Note that to use the webroot plugin, your server must be configured to serve files from hidden directories. If /.well-known is treated specially by your webserver configuration, you might need to modify the configuration to ensure that files inside /.well-known/acme-challenge are served by the webserver.

#################################

Regards

 

[lsfoo]

That looks more like a warning than an issue - did you encounter any problems?

 

[cyberpersons]

IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: example.com
Type: connection
Detail: Fetching
http://example.com/.well-known/acme-challenge/dZdskVv8_w-QC8A6UeGvfAy1ndexfgYq6cllPiBwjP8:
Timeout

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A 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.

 

[cyberpersons]

This error occured, even though the /.well-know folder is present but litespeed was not able to read it because its hidden.

Litespeed reads everything else

 

[lsfoo]

Do you have some rules that may be blocking the request? I just created a test script within a hidden folder and it was fine.

 

[cyberpersons]

Do you have some rules that may be blocking the request? I just created a test script within a hidden folder and it was fine.

No thing, simple virtual host created from console, are you able to use certbot ?

 

[ckissi]

Double check your DNS records for that domain and also redirects in rewrite rules.

 

[cyberpersons]

Double check your DNS records for that domain and also redirects in rewrite rules.

DNS is working because domain is serving other files normally.


only letsencrypt verification test failed. Any specifc info i need to add in rewrites to make it work?

 

[ckissi]

post your certbot command here and your rewrite rules

 

[cyberpersons]

Double check your DNS records for that domain and also redirects in rewrite rules.

I dont use any rewrite rules.

certbot command used:
certbot certonly --webroot -w /var/htm -d example.com

 

[lsfoo]

@cyberpersons

A couple questions:

1. What OS are you using?
2. Is the webroot directory correct? In that is .well-known created in the correct subdirectory? Using our default vhost as an example, it is located at /usr/local/lsws/Example/, but files are served from /usr/local/lsws/Example/html/, so .well-known should be created at /usr/local/lsws/Example/html/.well-known/ in order to be served as example.com/.well-known/

 

[cyberpersons]

@cyberpersons

A couple questions:

1. What OS are you using?
2. Is the webroot directory correct? In that is .well-known created in the correct subdirectory? Using our default vhost as an example, it is located at /usr/local/lsws/Example/, but files are served from /usr/local/lsws/Example/html/, so .well-known should be created at /usr/local/lsws/Example/html/.well-known/ in order to be served as example.com/.well-known/

Thank you I was able to fix it.

Problem that it was not able to verify behind NAT. I had to use VPS.

 

[lsfoo]

Aha, glad you were able to figure it out!

Good to know.

 

[cyberpersons]

Aha, glad you were able to figure it out!

Good to know.

Just asking it should work behind NAT as well, because normal files are being served fine, only certbot is not able to perform verification.

 

[lsfoo]

CertBot compares the IP of the server with the IP of the hostname - is it possible that the NAT is not forwarding the IP?