After changing the values ​​of "chmod 750" to "chmod 755", letsencrypt works correctly. The problem is in the code, the certificate and the key do not move in the /shared/ssl/ directory. Pay attention to crt and cer values

[Pro100x3mal]

    After changing the values ​​of "chmod 750" to "chmod 755", letsencrypt works correctly.  The problem is in the code, the certificate and the key do not move in the /shared/ssl/ directory.  Pay attention to crt and cer values

-----END CERTIFICATE-----
[Wed 16 Nov 2022 12:19:09 PM UTC] Your cert is in: /shared/ssl//mydomain.com/mydomain.com.cer
[Wed 16 Nov 2022 12:19:09 PM UTC] Your cert key is in: /shared/ssl//mydomain.com/mydomain.com.key
[Wed 16 Nov 2022 12:19:09 PM UTC] The intermediate CA cert is in: /shared/ssl//mydomain.com/ca.cer
[Wed 16 Nov 2022 12:19:09 PM UTC] And the full chain certs is there: /shared/ssl//mydomain.com/fullchain.cer
[Wed 16 Nov 2022 12:19:09 PM UTC] _on_issue_success
Nginx reloaded.
nginx: [emerg] cannot load certificate "/shared/ssl/mydomain.com.crt": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/shared/ssl/mydomain.com.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Originally posted by @Pro100x3mal in https://github.com/haiwen/seafile-docker/issues/311#issuecomment-1316973827

[kirisakow]

Also, the issue https://github.com/haiwen/seafile-docker/issues/321, although closed, has not been addressed. The proposed workarounds (including by myself) cannot replace the regular installation process, and are not part of the documentation.