nginx Directives settings added to vhost.err instead vhost

Discussion in 'Installation/Configuration' started by Neptun, Jul 23, 2019.

  1. Neptun

    Neptun Member

    Dear all,
    i have an issue at my server with the nginx Directives settings what i have added at the control panel.

    The rules are not added to the domain.com.vhost at /etc/nginx/sites-available - instead the system had added the rules from the control panel nginx Directives to domain.com.vhost.err - which has no effect to the nginx server settings

    What i have done wrong here or how can it be fixed that the rules will be added to the correct vhost file from the ispconfig control panel?

    Thanks in advance
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    An .err file is generated when nginx refused to start with the new config. Check your directives for errors. If you want to see the error, rename the current vhost file to vhost.bak, rename the vhost.err file to vhost and restart bginx.
     
    Neptun likes this.
  3. Neptun

    Neptun Member

    okkk that makes sense - i love ispconfig more & more !

    i have the issue at my nextcloud - i have at the nginx directives the recommended settings from https://www.fox1.de/2017/03/15/nextcloud-ispconfig3-debian3-nginx/ inside - seems not working anymore for nextcloud 16
     

Share This Page