Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: argument --webroot-path/-w: expected one argument
root@srv494115:~# sudo certbot certonly --webroot -w /usr/local/lsws/App/html/ -d app.appnetsoo.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for app.appnetsoo.com
Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.
First, I moved your post to the Help category. Had you posted there you would have been asked to answer some questions for us to help. You provided most of that info anyway but some more info would be helpful. Please answer the questions from that form that I show below.
I am puzzled about the "argument" error. You show it before your Certbot command. Was it displayed after that Certbot command? Because the format of your command looks correct.
Although, the folder used for the -w option probably does not match the vhRoot folder in your LiteSpeed config for this domain and URI. The "404" in the error means your server replied with this "404 Not Found". Certbot places the challenge token in the -w folder so your server must be able to find it there when the Let's Encrypt server asks for it.
Please answer these as best you can
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Show output of certbot --version
Describe briefly how you installed Certbot (apt, snap, pip ...)
I am pretty sure too But, they thought it important enough to post it so wanted to be sure I understood what they meant
I know the current version of Certbot fails when that error is issued. But, I wasn't sure all prior versions did. If an older version just ignored the faulty -w the default webroot folder would cause a 404 as it would not match the LiteSpeed default. Admittedly, this is highly unlikely to be the cause of their 404. Much more likely related to my other explanation.
But, they thought it important enough to post it so wanted to be sure I understood what they meant