# Access to file denied Cert-chain **URL:** \ **Category:** Installation & Configuration\ **Created:** [July 27, 2021, 10:37am UTC](https://forum.collaboraonline.com/t/access-to-file-denied-cert-chain/498 "2021-07-27T10:37:19Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![bearon](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bearon](https://forum.collaboraonline.com/u/bearon)\ **Post date:** [September 2, 2021, 4:35pm UTC](https://forum.collaboraonline.com/t/access-to-file-denied-cert-chain/498/4 "2021-09-02T16:35:40Z")
I don’t think it’s the length of the path… `/etc/letsencrypt/live/` tends to be owned by root, and not accessible to anyone else (which is generally desirable, as you want private keys to be actually private). A couple of options on how to solve this situation are detailed here: [node.js - Let's encrypt SSL couldn't start by "Error: EACCES: permission denied, open '/etc/letsencrypt/live/domain.net/privkey.pem'" - Stack Overflow](https://stackoverflow.com/questions/48078083/lets-encrypt-ssl-couldnt-start-by-error-eacces-permission-denied-open-et) Another option is to set up a terminating reverse proxy, so the certificate handling is done by the reverse proxy (eg. Apache2 or nginx), and not by Collabora Online. --- _[View the full topic](https://forum.collaboraonline.com/t/access-to-file-denied-cert-chain/498)._