SSL config on .vhosts - ISPConfig protected folders

Could you provide some insight and recommendations. When using SSL config on .vhosts - ISPConfig protected folders function opens port 80, deletes cipher config and redirect. This blows the SSL config away making it a little too risky to give to an end user (client) - end user won't understand what happened. How would you recommend we handle this?

Seems as if you manually edited the vhost config file. Thes vhost files may not be edited manually, they are completely managed by ispconfig and ispconfig will remove all manual changes.

When you want to alter the default vhost template of an ispconfig server then copy the nginx vhost template from /usr/local/ispconfig/server/conf/ to /usr/local/ispconfig/server/conf-custom/ and edit the template in conf custom.

If you want to modify the nginx setup for a single website, then use the Nginx directives field of the website for that, you can also alter existing sections of the file by using the ###merge### directive. The generated vhost file may never be aleterd as all your changes will be removed anyway.
you can also alter