No problem I am happy to help.
Just as another "FYI" the error seen in your screenshot is most likely a bug we have identified as occuring when a cluster node is offline when instance configuration is run. This issue has been given the CR numbers 107658 & 105341 and will be addressed in the next version of Litespeed. This error can cause the instance config wizard to loop.... CR107571 addess that issue which is also fixed in the next version of Litespeed.
Hope this helps and please don't hesitate to contact us, via the forums or support, if you should have any issues or concerns with Litespeed.