You might want to enable an HTTP connection in App Volumes Manager, for example, when you upgrade App Volumes to the latest version, and want to install and test App Volumes immediately without configuring SSL certificates. You can enable the HTTP connection either when you are installing App Volumes Manager or after installation.

Note: Enable HTTP only in a non-production environment or if you are running App Volumes Manager behind a load balancer.

Enable an HTTP Connection in App Volumes Manager During Installation

You can enable an HTTP connection when you are installing App Volumes Manager.


  1. When you choose networks ports during App Volumes Manager installation, select the Allow Connections Over HTTP (insecure) option.
  2. Enter a value for the HTTP port or retain the default value of 80.


HTTP is enabled in App Volumes Manager and you can now deactivate SSL in the agent and configure the agent to communicate over HTTP. See Deactivate SSL in App Volumes Agent.

Enable HTTP in App Volumes Manager After Installation

To enable HTTP in App Volumes Manager after installation, modify the Nginx configuration file.

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.


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


  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;.
    Note: It is recommended that you set the server_name to the hostname URL used to access App Volumes Manager. This ensures that the HTTP request is sent to the desired App Volumes Manager server.
    server {
            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;
             # updated by clock.rb
             location ~* ^.+\.(woff|woff2|eot|svg|ttf|jpg|jpeg|gif|png|ico|zip|css|js|html|htm|json)$ {
                 expires max;
            location ~* ^.+\.(css|js|htm|html|json)$ {
                #expires 0; # expire immediately
                expires 5m;
            include location/api_redirect_location.conf;
            location / {
              try_files /index.html @manager;
            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.


App Volumes Manager now communicates over HTTP.

What to do next

Access the agent computer that communicates with this App Volumes Manager, navigate to HKEY_LOCAL_MACHINE> SYSTEM>CurrentControlSet>Services>SvService>Parameters, and update the Manager registry key with the appropriate port number ( 80 for HTTP).