Why disable CORS directive can not be saved in vhost file?

HI
I put below codes in the nginx Directives setting, and clicked save. after ispconfig finished applying the changes, I open the nginx Directives setting again, and see the below codes there. but open the vhost file of that website, the codes are not there.

more_set_headers 'Access-Control-Allow-Origin: *';
more_set_headers 'Access-Control-Allow-Methods: GET, POST, OPTIONS';
more_set_headers 'Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

if manually put the codes into vhost, it works. but ispconfig will remove the codes after saving changes.

 

No, you misunderstood my question. Nginx is running fine.
the issue here is ISPconfig can not save the code below I saved in nginx Directives. the vhost file has no that codes after saved.

more_set_headers 'Access-Control-Allow-Origin: *';
more_set_headers 'Access-Control-Allow-Methods: GET, POST, OPTIONS';
more_set_headers 'Access-Control-Allow-Headers: DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

 

I don't know why, but I put the codes into nginx.conf http section to make it working instead.
thanks

 

Is there a file in the vhost file directory with name ending in ".err"? If there is, ISPConfig renamed the vhost file to that, so you do not see the changes you made in the vhost file.
@till suggested a way to find out why nginx did not start with the changes, making ISPConfig do the renaming to make nginx start.

 

Is there a file in the vhost file directory with name ending in ".err"?
NO