Permission denied: Init: Can't open server private key file
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Permission denied: Init: Can't open server private key file
Running rhel 6.10
Just ran updates and since then, selinux 1 time stopped httpd from starting, even though the booleans look correct. Set selinux to permissive and httpd started, then setenforce back to 1 and it would good. About a week later, httpd died with error: httpd dead but pid file exists.
httpd/error_log showed me this: Permission denied: Init: Can't open server private key file
Seems to me that selinux may be the issue and that restorecon -RvF /etc/ssl/certs/
may be the answer. However, if someone has other thoughts, let me know.
Otherwise, I'd like to know what I would be walking into with using this command.
httpd/error_log showed me this: Permission denied: Init: Can't open server private key file
Seems to me that selinux may be the issue and that restorecon -RvF /etc/ssl/certs/
may be the answer. However, if someone has other thoughts, let me know.
Otherwise, I'd like to know what I would be walking into with using this command.
Running restorecon is the correct way to fix certs files permissions/context, so they can be used by httpd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.