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

Combine pem files #9864

Closed
mrx23dot opened this issue Dec 18, 2023 · 2 comments
Closed

Combine pem files #9864

mrx23dot opened this issue Dec 18, 2023 · 2 comments

Comments

@mrx23dot
Copy link

Please add an option to combine these files, or do it out of the box:

cat /etc/letsencrypt/live/web.itzgeek.com/cert.pem /etc/letsencrypt/live/web.itzgeek.com/privkey.pem > /etc/letsencrypt/live/web.itzgeek.com/web.pem

Since at least lighthttpd requires a combined fine for
ssl.pemfile= xxx.pem

There is a no point doing it manually,
and it's one more step that can go wrong in cron job.

Applicable to every version I guess.

@osirisinferi
Copy link
Collaborator

osirisinferi commented Dec 19, 2023

This has been requested many times before, the first one back in 2015 already:

#1201

#5643

#5087

Those issues also have very simple workarounds using simple scripts in deploy hooks. (Not that different than your own line of code, but using a deploy hook is key here to automate things.)

But I'm going to close this issue as a duplicate now, as the last issue I mentioned above is still open.

@gstrauss
Copy link

Since at least lighthttpd requires a combined fine for
ssl.pemfile= xxx.pem

@mrx23dot that is incorrect (and the server is named "lighttpd", a portmanteau of "light" and "httpd")

Since lighttpd 1.4.53 (released Jan 2019), lighttpd supports having a separate file for the private key:

$SERVER["socket"] == ":443" {
    ssl.engine = "enable"
    ssl.pemfile = "/path/to/site/fullchain.pem"
    ssl.privkey = "/path/to/site/privkey.pem"
}

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

No branches or pull requests

3 participants