NodeWorx appears to be blindly parsing for the term “SSL” in the domain’s Apache configuration.
Open a domain's Apache configuration for editing.
Add a comment with the word "SSL" in it.
[B]Ex:[/B] # Force SSL if the request is for secure.domain.com.
Do something with InterWorx-CP that causes an edit in the Apache configuration.
[B]Ex:[/B] Add a SSL certificate.[/LIST]After step #3, the Apache server is completely stopped because a parse error now exists in the domain's configuration.
SSL if the request is for secure.domain.com.
Avoid the term “SSL” in comments.
Force S.S.L if the request is for secure.domain.com.
Thanks for the bug report Jimp. We’ve reproduced the problem and added it to our bug system.