Stunnel 5.60 started via Stunnel TLS wrapper on Windows 10 machine doesn't seem to be working
Hi, I am trying to get Stunnel 5.60 started automatically as a service. My stunnel.conf is stored under C:\Program Files (x86)\stunnel\config works fine if I run stunnel.exe manually from CMD or bring up the GUI and reload configuration. Now I would like it to start automatically after reboots. I tried running stunnel.exe -install which installs the Stunnel TLS wrapper service. Starting the service does not however do anything. The "Path to execute" it installs for the service is "C:\Program Files (x86)\stunnel\config" -service -install. I don't see anything in the log. I can see that the stunnel.exe process is running in task manager. But running netstat -ao shows that no port is being listened to by the PID. Tried removing my stunnel.conf file and the service will still starts but stunnel doesn't seem to be doing anything. What could be the problem?
I am trying to get Stunnel 5.60 started automatically as a service. My stunnel.conf is stored under C:\Program Files (x86)\stunnel\config works fine if I run stunnel.exe manually from CMD or bring up the GUI and reload configuration.
Now I would like it to start automatically after reboots. I tried running stunnel.exe -install which installs the Stunnel TLS wrapper service. Starting the service does not however do anything. The "Path to execute" it installs for the service is "C:\Program Files (x86)\stunnel\config" -service -install.
You might try putting the configuration somewhere outside of "C:\Program Files (x86)". I've seen system reserved folders like that cause all sorts of permissions-related havoc in situations like that on Windows. You might try it in your own user folder, or perhaps in a new "C:\Stunnel" folder or something along those lines. -Dave
Thanks for the suggestion. Found out the issue I think. I have my cert and key, and CA cert in a different directory then the config file (under stunnel\config). Though I point to them from the config file using full path, it doesn't work when started as service. It's working fine if I start manually from command line. So, moving my cert/key and CA cert to the config directory, and then remove all the paths in the config file, specifying only the file name of the certs and key made it work.
participants (2)
-
Dave -
ling＠aliko.com