# Coolwsd failed with let's encrypt?

**URL:** <https://forum.collaboraonline.com/t/coolwsd-failed-with-lets-encrypt/2502>\
**Category:** Installation & Configuration\
**Created:** [March 28, 2024, 12:17am UTC](https://forum.collaboraonline.com/t/coolwsd-failed-with-lets-encrypt/2502 "2024-03-28T00:17:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Tex](https://avatars.discourse-cdn.com/v4/letter/t/eb8c5e/32.png) [@Tex](https://forum.collaboraonline.com/u/Tex)\
**Post date:** [March 28, 2024, 1:08am UTC](https://forum.collaboraonline.com/t/coolwsd-failed-with-lets-encrypt/2502/2 "2024-03-28T01:08:46Z")

</div>

Hey @FredMa01, welcome to the forum and thanks for the question. 🙂

> [@FredMa01](#):
>
> Failed to initialize COOLWSD: Access to file denied: /etc/letsencrypt/live/mydomain/fullchain.pem

Hmmm, back in 2021, @bearon gave an answer to a similar problem:

> [@Access to file denied Cert-chain](https://forum.collaboraonline.com/t/access-to-file-denied-cert-chain/498/4):
>
> 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 certi…

It could be Debian has the permissions locked as the “root” user, so you might have to try a few extra things.

Also, what version of Debian are you using?

---

_[View the full topic](https://forum.collaboraonline.com/t/coolwsd-failed-with-lets-encrypt/2502)._