Skip to main content
added 8 characters in body
Source Link
muru
  • 78.1k
  • 16
  • 213
  • 319

Generally you should not use the archive directory. The current ssl files are symlinked so that is what should be used. For nginx I think the cfg statements would be:

ssl_certificate /etc/letsencrypt/live/www.example.tech/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/www.example.tech/privkey.pem

ssl_certificate     /etc/letsencrypt/live/www.example.tech/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/www.example.tech/privkey.pem

Afraid I don't know what the haproxy equivilent would be.

Generally you should not use the archive directory. The current ssl files are symlinked so that is what should be used. For nginx I think the cfg statements would be:

ssl_certificate /etc/letsencrypt/live/www.example.tech/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/www.example.tech/privkey.pem

Afraid I don't know what the haproxy equivilent would be.

Generally you should not use the archive directory. The current ssl files are symlinked so that is what should be used. For nginx I think the cfg statements would be:

ssl_certificate     /etc/letsencrypt/live/www.example.tech/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/www.example.tech/privkey.pem

Afraid I don't know what the haproxy equivilent would be.

Source Link
user103944
  • 410
  • 2
  • 4

Generally you should not use the archive directory. The current ssl files are symlinked so that is what should be used. For nginx I think the cfg statements would be:

ssl_certificate /etc/letsencrypt/live/www.example.tech/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/www.example.tech/privkey.pem

Afraid I don't know what the haproxy equivilent would be.