Invalid root challenges validation directory


#1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:www.yoursportsleague.com

I ran this command:/usr/local/bin/certbot-auto renew

It produced this output:…2018-04-30 02:17:31,650:DEBUG:certbot.plugins.webroot:Creating root challenges validation dir at /opt/tomcat7/webapps/ysl/.well-known/acme-challenge
2018-04-30 02:17:31,651:DEBUG:certbot.error_handler:Encountered exception:
Traceback (most recent call last):
File “/opt/eff.org/certbot/venv/lib64/python3.4/site-packages/certbot/auth_handler.py”, line 73, in handle_authorizations
resp = self._solve_challenges(aauthzrs)
File “/opt/eff.org/certbot/venv/lib64/python3.4/site-packages/certbot/auth_handler.py”, line 124, in _solve_challenges
resp = self.auth.perform(all_achalls)
File “/opt/eff.org/certbot/venv/lib64/python3.4/site-packages/certbot/plugins/webroot.py”, line 78, in perform
self._create_challenge_dirs()
File “/opt/eff.org/certbot/venv/lib64/python3.4/site-packages/certbot/plugins/webroot.py”, line 168, in _create_challenge_dirs
stat_path = os.stat(path)
FileNotFoundError: [Errno 2] No such file or directory: ‘/opt/tomcat7/webapps/ysl’

My web server is (include version): Apache 2.2.31

The operating system my web server runs on is (include version): Centos 6.9

My hosting provider, if applicable, is: eApps

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): no


#2

So the problem is that the directory /opt/tomcat7/webapps/ysl does not exist. Where is the path to the root challenges validation directory set? Can I change it so this certificate will auto renew?


#3

Hi @stevencwillett,

It is defined in a conf file for your domain in /etc/letsencrypt/renewal/ so edit the file and replace wrong path.

Cheers,
sahsanu


#4

Thanks, sahsanu - problem resolved!


#5

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