Hi all,
I have installed Stunnel 5.56 win64 on a fully updated Windows 10 machine to work with Blue Iris. Stunnel operates well when I manually start it however I cannot get it to work automatically after a reboot.
I have run the run the “stunnel Service Install” and “stunnel Service Start” shortcuts supplied, and in the first instance the service installs and starts. I can then connect through Stunnel to my Blue Iris server.
I have found that after I reboot, the Stunnel service appears to start automatically but it is not functional. I cannot connect through it to Blue Iris. Stunnel is visible and Running in the Windows 10 Services list (from services.msc) and the Windows Task Manager shows a Process and Service active.
To rectify this I can manually issue the “stunnel Service Stop”, followed by the “stunnel Service Start” shortcuts and the service becomes functional again.
I have tried turning on debug info and the stunnel log file in stunnel.conf and see that log entries only begin after I have done the stop/start manual process.
Thanks for any insight to what I’m sure I am missing here.
Rod
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
Ho Rod,
Maybe the stunnel service is starting too early. You may want create a service dependency on another service like the DNS client, to delay the start and be sure any Tcp/ip stack dependencies are ready.
regards Jose
On Aug 14, 2020, at 4:20 PM, Rod Marr [email protected] wrote:
Hi all,
I have installed Stunnel 5.56 win64 on a fully updated Windows 10 machine to work with Blue Iris. Stunnel operates well when I manually start it however I cannot get it to work automatically after a reboot.
I have run the run the “stunnel Service Install” and “stunnel Service Start” shortcuts supplied, and in the first instance the service installs and starts. I can then connect through Stunnel to my Blue Iris server.
I have found that after I reboot, the Stunnel service appears to start automatically but it is not functional. I cannot connect through it to Blue Iris. Stunnel is visible and Running in the Windows 10 Services list (from services.msc) and the Windows Task Manager shows a Process and Service active.
To rectify this I can manually issue the “stunnel Service Stop”, followed by the “stunnel Service Start” shortcuts and the service becomes functional again.
I have tried turning on debug info and the stunnel log file in stunnel.conf and see that log entries only begin after I have done the stop/start manual process.
Thanks for any insight to what I’m sure I am missing here.
Rod
Sent from Mail for Windows 10
stunnel-users mailing list [email protected] https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
Jose, thanks so much. That solved the problem.
In Windows 10 SERVICES.MSC for Stunnel I set the Start Up Type to “Automatic (Delayed Start)”. At boot time this queues the services set that way to start after the core services are running – including the TCP/IP stack.
All good now and my Stunnel/Blue Iris experience has improved greatly.
Thanks again, Rod
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Josealf.rmmailto:[email protected] Sent: Friday, August 14, 2020 9:06 PM To: Rod Marrmailto:[email protected] Cc: [email protected]mailto:[email protected] Subject: Re: [stunnel-users] Stunnel 5.56 Windows 10 Service - Not functioning after Reboot
Ho Rod,
Maybe the stunnel service is starting too early. You may want create a service dependency on another service like the DNS client, to delay the start and be sure any Tcp/ip stack dependencies are ready.
regards Jose
On Aug 14, 2020, at 4:20 PM, Rod Marr <[email protected]mailto:[email protected]> wrote: Hi all,
I have installed Stunnel 5.56 win64 on a fully updated Windows 10 machine to work with Blue Iris. Stunnel operates well when I manually start it however I cannot get it to work automatically after a reboot.
I have run the run the “stunnel Service Install” and “stunnel Service Start” shortcuts supplied, and in the first instance the service installs and starts. I can then connect through Stunnel to my Blue Iris server.
I have found that after I reboot, the Stunnel service appears to start automatically but it is not functional. I cannot connect through it to Blue Iris. Stunnel is visible and Running in the Windows 10 Services list (from services.msc) and the Windows Task Manager shows a Process and Service active.
To rectify this I can manually issue the “stunnel Service Stop”, followed by the “stunnel Service Start” shortcuts and the service becomes functional again.
I have tried turning on debug info and the stunnel log file in stunnel.conf and see that log entries only begin after I have done the stop/start manual process.
Thanks for any insight to what I’m sure I am missing here.
Rod
_______________________________________________ stunnel-users mailing list [email protected]mailto:[email protected] https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-usershttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.stunnel.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstunnel-users&data=02%7C01%7C%7C6bdee7654fa84a935fc608d840b77aec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637330504065435460&sdata=1aJBhZTTMFKr2bIG68yCwSXubsKPtUvmae4TBou79ts%3D&reserved=0
-
Josealf.rm -
Rod Marr