"ssl_port" may be working when "port" isn't

Version 1.47

Bugfix
Finished

If DA is already running on port 2222, and ssl_port=2223 is set, it's possible that a "start" of DA will fail with the "cannot bind to 2222" error, but the ssl_port starts up fine. This can prevent the dataskq from noticing directadmin isn't running on 2222, since it's running on 2223. I'm not 100% sure on the exact scenario, but it is possible (it's been reported) The fix is to have the master daemon kill the ssl deamon child if it fails.. bring everything down if 2222 doesn't work.

Interested to try DirectAdmin? Get a 30-day Free Trial!