Enable HTTP in App Volumes Manager After Installation

You can modify the Nginx configuration file in App Volumes Manager if you want to enable HTTP in the manager after it has been installed.

Important: This server block is not present in the Nginx file by default; add this server block only if you have not enabled HTTP when installing App Volumes Manager.

Prerequisites

Navigate to C:\Program Files (x86)\CloudVolumes\Manager\nginx\conf and take a back up of the existing Nginx configuration file, nginx.conf.

Procedure

1. Log in as administrator to the machine where App Volumes Manager is installed.
2. Navigate to C:\Program Files (x86)\CloudVolumes\Manager\nginx\conf, open the Nginx configuration file, and copy the following block in the Nginx file after include proxy/vcenter*.conf;.

   server {
           server_name  0.0.0.0;
           listen       80;
           listen       [::]:80;
           
   
           root   ../public;
           rewrite ^/(.*)/$ /$1 permanent;
   
           access_log  logs/access_http.log  main;
           error_log   logs/error_http.log  info;
   
           charset utf-8;
           override_charset on;
   
           gzip on;
           gzip_types application/json application/javascript;
   
           error_page  404              /404.html;
          error_page  502              /502.html;
           #error_page   500 502 503 504  /500.html;
   
           location ~* ^.+\.(jpg|jpeg|gif|png|ico)$ {
               expires max; 
               break;
           }
   
           location ~* ^.+\.(css|js|htm|html|json)$ {
               #expires 0; # expire immediately
               expires 5m;
               break;
           }
   
           location / {
             try_files /index.html @manager;
           }
   
           location ^~ /ngvc/ {
               access_log logs/access_ngvc_http.log  main;
               error_log logs/error_ngvc_http.log  info;
               proxy_connect_timeout 10;
               #proxy_next_upstream off;
               proxy_next_upstream timeout;
               proxy_read_timeout 600;
               proxy_send_timeout 30;
               send_timeout 30;
               proxy_redirect off;
               server_name_in_redirect off;
               proxy_pass_header Cookie;
               proxy_pass_header Set-Cookie;
               proxy_pass_header X-Accel-Redirect;
               proxy_set_header Host $host:80;
               proxy_set_header X-Real-IP $remote_addr;
               proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
               add_header X-Backend $upstream_addr;
               proxy_pass http://ngvc;
           }
   
           location @manager {
               proxy_connect_timeout 10;
               #proxy_next_upstream off;
               proxy_next_upstream timeout;
               proxy_read_timeout 600;
               proxy_send_timeout 30;
               send_timeout 30;
               proxy_redirect off;
               server_name_in_redirect off;
               proxy_pass_header Cookie;
               proxy_pass_header Set-Cookie;
               proxy_pass_header X-Accel-Redirect;
               proxy_set_header Host $host:80;
               proxy_set_header X-Real-IP $remote_addr;
               proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
               add_header X-Backend $upstream_addr;
               add_header X-Frame-Options SAMEORIGIN;
               add_header X-Content-Type-Options nosniff;
               add_header X-XSS-Protection "1; mode=block";
               proxy_pass http://manager;
           }
       }
   

3. Restart the App Volumes service.

Results

App Volumes Manager now communicates over HTTP.