Use an internal certificate

[Malo-PVEY]

Hello,

If I don’t use the “TLS_DOMAIN” option to obtain a self-signed Let’s Encrypt certificate, is it possible to use an existing certificate?
If so, could you provide a link to the documentation explaining how to set it up?

Thank you

[pglombardo]

Hi @Malo-PVEY - custom certificates aren't possible currently out of the box.

You can setup a Proxy in front (NPM, nginx, Caddy) and point the backend to http://your-ip:5100

The Docker container exposes port 5100 for plain HTTP traffic. If you go this route, make sure that proxy X-Forwarded-For headers are passed to the backend: https://docs.pwpush.com/docs/proxies/

[Malo-PVEY]

Thank you for your reply.

Could you quickly explain how the PasswordPusher ports work?
I don't understand why we need to open ports 80, 443, and 5100.

Thanks again.

[pglombardo]

If you use TLS_DOMAIN, only port 443 needs to be open. port 80 (HTTP) is to support older browsers but we may remove this soon.

Port 5100 is HTTP and for when the application is hosted behind a proxy.

These are the ports that the Docker container exposes. You can configure which you expose on your host in the docker-compose.yml.

[pglombardo]

Created #4390 as a possible improvement. It defaults to TLS_DOMAIN usage for new installs. Users can uncomment if they want the other ports.