Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL with Let's Encrypt #18

Open
Sawrz opened this issue Apr 19, 2020 · 2 comments
Open

SSL with Let's Encrypt #18

Sawrz opened this issue Apr 19, 2020 · 2 comments

Comments

@Sawrz
Copy link

Sawrz commented Apr 19, 2020

Hi,
In your docs, you mention the SSL certs need to have a specific name. However, I use let's encrypt, which gives my certificates names by itself. Renaming the certs each time those renew would be a very tedious, repetitive and unnecessary task.
Is there a way to let the container search for a different naming scheme? Like the domain name given in FIRST_DOMAIN?

Maybe there is an environment variable to specify the name and you don't mention it here? Either way, it would make the maintenance much smoother =)

@Carazyda
Copy link
Member

Hello @Sawrz we don't have env variables for this, but you can try using a symlink to certs in your OS.

@razorness
Copy link

Symlink is not working. You will have to copy your pems to /app/onlyoffice/MailServer/data/certs:

  • fullchain.pem -> mail.onlyoffice.ca-bundle
  • privkey.pem -> mail.onlyoffice.key
  • cert.pem -> mail.onlyoffice.crt

You have to write a small script to copy your certs and restart docker container resp. mail server as part of a renew hook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants