NEXT.JS HESTIACP COMPATIBILITY

1

Hi, good day.
I realised that the only way to use next.js(node.js like) apps on hestiacp is through your custom templates.
The problem now is that once I start using the custom template, many other features like awstats, dashboard statistics stop working.
Please what’s the way out. Thanks

2

@ddudkin were you able to solve the vstat problem? Thanks as you respond

3

Please share the current template you are using…

4

Thank you. This is the current template

server {
    listen      %ip%:%proxy_port%;
    server_name %domain_idn% %alias_idn%;

    include %home%/%user%/conf/web/%domain%/nginx.forcessl.conf*;

    location = /favicon.ico { access_log off; log_not_found off; }

    # Maximum file upload size.
    client_max_body_size 6400M;

    # AWStats configuration
    location /vstats/ {
        alias /usr/lib/cgi-bin/;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME /usr/lib/cgi-bin/awstats.pl;
        fastcgi_pass unix:/var/run/fcgiwrap.socket;
        fastcgi_index awstats.pl;
    }

    location /vstats/icon/ {
        alias /usr/share/awstats/icon/;
    }

     access_log /var/log/nginx/domains/domain.tld.log;

    # Serve static files from public_html/public
    location / {
        alias %home%/%user%/web/%domain%/public_html/
s $uri $uri/ @proxy;
        access_log off;
        expires max;
    }

    location / {
        proxy_pass  http://127.0.0.1:4001;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_pass_request_headers on;
    }

    location /error/ {
        alias   %home%/%user%/web/%domain%/document_errors/;
    }

    location @fallback {
        proxy_pass      http://%ip%:%web_port%;
    }

    location ~ /\.ht    {return 404;}
    location ~ /\.svn/  {return 404;}
    location ~ /\.git/  {return 404;}
    location ~ /\.hg/   {return 404;}
    location ~ /\.bzr/  {return 404;}

    include %home%/%user%/conf/web/%domain%/nginx.conf_*;
}
5

I’m still anticipating an answer. I hope there is really a way out