Stunnel does not Startup with Connect

Problem: stunnel does not start up with Connect

Although stunnel can be installed as a service, it doesn’t load the stunnel.conf file(!) one workaround is to not setup the services to run automatically but to auto-run these batch files at startup:

Note: This tech-note assumes stunnel is installed in c:\Connect\\; be sure to adapt the scripts accordingly.

Origin server startup.bat:

net start FMS
net start FMSAdmin
net start ConnectPro
net start CPTelephonyService
c:\Connect\\stunnel\stunnel.exe stunnel.conf
@ECHO OFF Origins stop.bat:

net stop ConnectPro
net stop CPTelephonyService
net stop FMSAdmin
net stop FMS /y

If you have remote Edge servers, use these; they includes cache clearing maintenance.

Edges start.bat:

net start fms
ping -n 1 -w 10000>nul
net start fmsadmin
c:\breeze\edgeserver\stunnel\stunnel.exe stunnel.conf

Edges stop.bat:

net stop fmsadmin
ping -n 1 -w 10000>nul
net stop fms
ping -n 1 -w 20000>nul
del /Q /S c:\breeze\edgeserver\win32\cache\http\*.*
ping -n 1 -w 10000>nul

Run > gpedit.msc
Local Computer Policy > Computer Configuration > Windows Settings > Scripts (Startup/Shutdown)
Batch files are assigned as startup & shutdown scripts. This is in addition to being available to be run manually.

One Response to Stunnel does not Startup with Connect

  1. Georgina says:

    Thanks for sharing your thoughts about pattern.