Log into your account at Azure Portal. Go to “Virtual Machines” in the left menu. Click “Add” and search for “Varnish Software”. You will see a list of all our products.
That’s it. Your Varnish Software instance is up and running. Next, tune up your configuration and start enjoying the product benefits.
For Windows SSH client, you may use Putty. For Linux and Mac users, you may use your favorite SSH client.
For more information on how to access your Linux instance on AWS, please see;
The configuration files are located in different places based on what kind of VMs you are running, that is: VAC, VCS, Varnish Cache (VC), Varnish Cache Plus (VCP) or Varnish Enterprise (VE).
In this section, we cover the configuration basics. For more details and advanced configuration possibilities, please refer to the materials in the following links
VAC should run out of the box without any additional effort.
By default, the
varnishd process should be running on
TCP 6081. If you have a VAC instance running in your environment, you can configure
varnish-agent to talk to VAC to see some graphs and be able to deploy Varnish Configuration Language (VCL) files to all registered Varnish Cache nodes via the VAC RESTful API.
Note: as of August 2017, “Varnish Cache 5.1” is not yet compatible with other products provided by Varnish Software. Development on compatibility is underway.
VCP or VE is the enterprise version of Varnish Cache (VC). Apart from ease-of-use improvements and performance enhancements, VCP also provides additional functionality, such as Varnish Massive Storage Engine (MSE), Varnish High Availability (VHA) and SSL/TLS backend support. Customers can also enable frontend SSL/TLS by using Varnish Plus Addon SSL (Hitch), which is also included with the image.
VCS should be running out of the box without any additional effort.
Point your browser to your instance
hostname/ip address (You can find this in the Azure Portal) (
http://184.108.40.206 for this example.) and you will be able to access VAC login page. The default username is
vac and the default password can be found at
/root/vac_init_password. You need to
SSH to the instance to retrieve the password.
After clicking the “Sign In” button, you should see a dashboard looks like the following figure 4.
o verify that VCS is running, point your browser to the
hostname/ip address to the
TCP 6555 (
http://220.127.116.11:6555 from an example above). you can see the VCS dashboard without any issues or problems such as the one in figure 5, without any authentication.
In VC/VCP/VE instances, there should be two
varnishd processes running out of the box, if you
SSH to the instances to verify the process table. However, you can simply verify the process status by running
curl from your terminal to
terminal$ curl 18.104.22.168:6081 <!DOCTYPE html> <html> <head> <title>503 Backend fetch failed</title> </head> <body> <h1>Error 503 Backend fetch failed</h1> <p>Backend fetch failed</p> <h3>Guru Meditation:</h3> <p>XID: 6</p> <hr> <p>Varnish cache server</p> </body> </html> terminal$ curl -I 22.214.171.124:6081 HTTP/1.1 503 Backend fetch failed Date: Thu, 17 Nov 2016 12:53:23 GMT Server: Varnish Content-Type: text/html; charset=utf-8 Retry-After: 5 X-Varnish: 32773 Age: 0 Via: 1.1 varnish-v4 Connection: keep-alive
varnishd is now running nicely. You should not be worried about the
503 Backend fetch failed message at all. This is an expected behavior. In order to hit a cache or a web page with
200 OK, you need to assign a running web server backend to a default VCL configuration, located at
If you see a
connection refuse error, that means that the process is not running for some reason. You can fix this by running a restart command. Then
curl to check again.
terminal$ ssh 126.96.36.199 "sudo service varnish restart" * Stopping HTTP accelerator varnish No /usr/sbin/varnishd found running; none killed. ...fail! * Starting HTTP accelerator varnish ...done. terminal$ ssh 188.8.131.52 "netstat -nlt" Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:6081 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:6082 0.0.0.0:* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::6081 :::* LISTEN
Configure a location of web server backend, you have to
SSH to the instance and edit
/etc/varnish/default.vcl, adding a backend and define your VCL caching rules.
terminal$ sudo vi /etc/varnish/default.vcl
varnishd service to active the current configuration.
terminal$ sudo service varnish restart
Update your site’s DNS record to be a
hostname/ip address of the running Varnish Cache (VC), Varnish Cache Plus (VCP) or Varnish Enterprise (VE) instances. After making changes in the DNS record (allowing for DNS ttl expiry), traffic will start coming to this instance.
For more advanced features and usage for VCP, please refer to the following documentation:
Please contact Varnish Software The Cloud Team, if your instance is not running as expected. We are eager to help you to fix you your issue/problem as early as possible.
Customers who purchase VAC, VCP, VCS or VE VM images on the Microsoft Azure are eligible for Varnish Cloud support and software updates provided by the Varnish Software, Inc. engineering team. To contact support, please submit the Varnish Cloud Support Activation form.
Please visit the Post Configuration for more information you can do with Varnish Cloud products. For example:
varnish-agentto comunicate with
vstatdprobeto forward data to