I'm setting up a new ubuntu server and it includes stunnel version 5.74. My ultimate goal is to have the service managed by systemd. Things didn't really work out of the box because of the needed configuration file which I was able to use from an existing didn't have the appropriate information in it. So, even though it would start (using initd), when I would try to stop it, it wouldn't. This turned out to be pretty straightforward solve by adding the following to my one and only conf file: setuid = stunnel4 setgid = stunnel4 ; PID file is created inside the chroot jail (if enabled) pid = /var/run/stunnel4/stunnel4.pid While the example file in /usr/share/doc/stunnel4/examples/stunnel.conf-sample had these entries in the file, they were commented out and I wasn't sure if that those were actual defaults, or needed to be uncommented for production. The later seemed to be the case. After fixing that, I was able to use systemctl start/stop as normal, however I noticed that it was being started by the old initd setup. #system status stunnel4 ● stunnel4.service - LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons) Loaded: loaded (/etc/init.d/stunnel4; generated) Active: active (running) since Tue 2026-02-24 20:35:35 CST; 2s ago Invocation: 343fad33bfb949aa8b48285e37c7f05a Docs: man:systemd-sysv-generator(8) Process: 4754 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=0/SUCCESS) Tasks: 4 (limit: 4367) CPU: 192ms CGroup: /system.slice/stunnel4.service So after further searching I found the following files: /usr/lib/systemd/system/stunnel.target /usr/lib/systemd/system/stunnel@.service I executed the command: systemctl enable stunnel@myconffile When I use this command: systemctl start stunnel@myconffile It definitely executes the correct command, but then the whole service shuts down and I get this: ○ stunnel@myconffile.service - TLS tunnel for network daemons - per-config-file service Loaded: loaded (/etc/systemd/system/stunnel@.service; enabled; preset: enabled) Active: inactive (dead) since Tue 2026-02-24 20:44:54 CST; 11s ago Duration: 20.157s Invocation: 46cddb34062b401b87e8516f47b1482b Docs: man:stunnel4(8) Process: 5099 ExecStart=/usr/bin/stunnel4 /etc/stunnel/attuverse.conf (code=exited, status=0/SUCCESS) Main PID: 5099 (code=exited, status=0/SUCCESS) CPU: 128ms No stunnel service is running. There wasn't anything in the log that I could find that would indicate why it stopped. if I execute this command: /usr/bin/stunnel4 /etc/stunnel/myconffile.conf It works how I would expect it to. For now I'm using the initd initialization, but I would love to get the systemd version running. Anyone have some suggestions? Thanks. Mike