Having a problem with setup of a new seafile instance. It works fine without SSL, but when I turn SEAFILE_SERVER_LETSENCRYPT on, I get the following in the log files:
[2022-05-19 20:05:45] Preparing for letsencrypt ...
[2022-05-19 20:05:45] Found existing cert file /shared/ssl/mydomain.com.crt
Certificate will expire
[2022-05-19 20:05:45] Starting letsencrypt verification
fatal: unable to connect to github.com:
github.com[0: 140.82.113.3]: errno=Connection timed out
Traceback (most recent call last):
File "/scripts/start.py", line 86, in <module>
main()
File "/scripts/start.py", line 51, in main
init_letsencrypt()
File "/scripts/bootstrap.py", line 67, in init_letsencrypt
call('/scripts/ssl.sh {0} {1}'.format(ssl_dir, domain))
File "/scripts/utils/__init__.py", line 68, in call
return subprocess.check_call(*a, **kw)
File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/scripts/ssl.sh /shared/ssl mydomain.com' returned non-zero exit status 1
*** /scripts/start.py exited with status 1.
fatal: unable to connect to github.com:
github.com[0: 140.82.113.3]: errno=Connection timed out
Could this be the due to the problem found in https://github.com/haiwen/seafile-docker/issues/290, where the call to github is made with http instead of https? If so, how would I fix it? Is there a way for me to get into the docker image and edit the script there, or is this another problem entirely?
