Pro edition + docker + letsencrypt does not start on expired cert

Hello there ,
I’ve restarted my seafile instance , but I didn’t noticed that the cert expired yesterday and still wasn’t renewed .

Now it can’t start the instance because the certificate is expired

Traceback (most recent call last):
  File "/shared/ssl/letsencrypt/", line 198, in <module>
  File "/shared/ssl/letsencrypt/", line 194, in main
    signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER,, disable_check=args.disable_check, directory_url=args.directory_url,
  File "/shared/ssl/letsencrypt/", line 144, in get_crt
    raise ValueError("Wrote file to {0}, but couldn't download {1}: {2}".format(wellknown_path, wellknown_url, e))
ValueError: Wrote file to /var/www/challenges/guli5qrag5jis4613ixxTTKa-5rwQG2T6s5ZQ7-Cxgo, but couldn't download Error:
Data: None
Response Code: None
Response: <urlopen error [Errno 110] Connection timed out>
Traceback (most recent call last):
  File "/scripts/", line 86, in <module>
  File "/scripts/", line 51, in main
  File "/scripts/", line 67, in init_letsencrypt
    call('/scripts/ {0} {1}'.format(ssl_dir, domain))
  File "/scripts/utils/", line 68, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python2.7/", line 541, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/scripts/ /shared/ssl' returned non-zero exit status 1
*** /scripts/ exited with status 1.
*** Shutting down runit daemon (PID 35)...
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...

How can I circumvent this and start the instance correctly ?

see issue #78 into the seafile haiwen/seafile-docker repo on github

Usually there is a problem in your nginx/apache conf or in file/folder permissions if letsencrypt doesn’t work. But I don’t really know how the docker version is built

it’s the official image for pro , so from this point of view I think is aligned with the community one