Configuring my own certificate SSL in seafile pro deployed with docker

Hey @shoeper please elaborate … Why not use sslforfree is it bad?

Because in case the services gets hacked all private keys (created while the service is hacked) can be stolen.

They state “Private Keys are generated in your browser and never transmitted.” but also make the exception that keys are generated on their server in case your browser doesn’t support it.

1 Like

I am aware of this, but my goal was to configure my own certificates on an internal network without access to the outside.

Now I have another problem, I can not configure tls authentication with active directory, with docker it’s all more complicated.