Description: It is not possible to use tls together with a systemd upstart job because it needs elevated permissions with is too much of a security hole for us
To reproduce Install redis-server on any Linux system, all goes well, then configure with tls
Expected behavior sudo systemctl restart redis-server should restart it with tls support
Additional information The only error messages I see are these Oct 15 13:20:15 RedisSentinel1 systemd[1]: redis-server.service: Start request repeated too quickly. Oct 15 13:20:15 RedisSentinel1 systemd[1]: redis-server.service: Failed with result 'protocol'.
I have tested this on Ubuntu Server 24.04, Debian Bookworm and Fedora Server 40 - the issue is identical on each set up If instead I use the following command
sudo /usr/bin/redis-server /etc/redis.conf then it works perfectly, the problem seems to be with the user redis is running as and running it as root would be suicide on a production system
Comment From: scothost
I fixed it myself - feel free to close this
my cert files were in my home folder, I moved them to /etc/redis/