---
layout: default
navsection: installguide
title: Install Keep-web server
...
{% comment %}
Copyright (C) The Arvados Authors. All rights reserved.

SPDX-License-Identifier: CC-BY-SA-3.0
{% endcomment %}

The Keep-web server provides read/write HTTP (WebDAV) access to files stored in Keep. It serves public data to unauthenticated clients, and serves private data to clients that supply Arvados API tokens. It can be installed anywhere with access to Keep services, typically behind a web proxy that provides TLS support. See the "godoc page":http://godoc.org/github.com/curoverse/arvados/services/keep-web for more detail.

By convention, we use the following hostnames for the Keep-web service:

<notextile>
<pre><code>download.<span class="userinput">uuid_prefix</span>.your.domain
collections.<span class="userinput">uuid_prefix</span>.your.domain
*.collections.<span class="userinput">uuid_prefix</span>.your.domain
</code></pre>
</notextile>

The above hostnames should resolve from anywhere on the internet.

h2. Install Keep-web

Typically Keep-web runs on the same host as Keepproxy.

On Debian-based systems:

<notextile>
<pre><code>~$ <span class="userinput">sudo apt-get install keep-web</span>
</code></pre>
</notextile>

On Red Hat-based systems:

<notextile>
<pre><code>~$ <span class="userinput">sudo yum install keep-web</span>
</code></pre>
</notextile>

Verify that @Keep-web@ is functional:

<notextile>
<pre><code>~$ <span class="userinput">keep-web -h</span>
Usage of keep-web:
  -config file
    	Site configuration file (default may be overridden by setting an ARVADOS_CONFIG environment variable) (default "/etc/arvados/config.yml")
  -dump-config
    	write current configuration to stdout and exit
[...]
  -version
    	print version information and exit.
</code></pre>
</notextile>

h3. Set up a reverse proxy with TLS support

The Keep-web service will be accessible from anywhere on the internet, so we recommend using TLS for transport encryption.

This is best achieved by putting a reverse proxy with TLS support in front of Keep-web, running on port 443 and passing requests to Keep-web on port 9002 (or whatever port you chose in your run script).

Note: A wildcard TLS certificate is required in order to support a full-featured secure Keep-web service. Without it, Keep-web can offer file downloads for all Keep data; however, in order to avoid cross-site scripting vulnerabilities, Keep-web refuses to serve private data as web content except when it is accessed using a "secret link" share. With a wildcard TLS certificate and DNS configured appropriately, all data can be served as web content.

For example, using Nginx:

<notextile><pre>
upstream keep-web {
  server                127.0.0.1:<span class="userinput">9002</span>;
}

server {
  listen                <span class="userinput">[your public IP address]</span>:443 ssl;
  server_name           download.<span class="userinput">uuid_prefix</span>.your.domain
                        collections.<span class="userinput">uuid_prefix</span>.your.domain
                        *.collections.<span class="userinput">uuid_prefix</span>.your.domain
                        ~.*--collections.<span class="userinput">uuid_prefix</span>.your.domain;

  proxy_connect_timeout 90s;
  proxy_read_timeout    300s;

  ssl                   on;
  ssl_certificate       <span class="userinput"/>YOUR/PATH/TO/cert.pem</span>;
  ssl_certificate_key   <span class="userinput"/>YOUR/PATH/TO/cert.key</span>;

  location / {
    proxy_pass          http://keep-web;
    proxy_set_header    Host            $host;
    proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;

    client_max_body_size    0;
    proxy_http_version      1.1;
    proxy_request_buffering off;
  }
}
</pre></notextile>

{% include 'notebox_begin' %}
If you restrict access to your Arvados services based on network topology -- for example, your proxy server is not reachable from the public internet -- additional proxy configuration might be needed to thwart cross-site scripting attacks that would circumvent your restrictions. Read the "'Intranet mode' section of the Keep-web documentation":https://godoc.org/github.com/curoverse/arvados/services/keep-web#hdr-Intranet_mode now.
{% include 'notebox_end' %}

h3(#dns). Configure DNS

Configure your DNS servers so the following names resolve to your Nginx proxy's public IP address.
* @download.uuid_prefix.your.domain@
* @collections.uuid_prefix.your.domain@
* @*--collections.uuid_prefix.your.domain@, if you have a wildcard TLS certificate valid for @*.uuid_prefix.your.domain@ and your DNS server allows this without interfering with other DNS names.
* @*.collections.uuid_prefix.your.domain@, if you have a wildcard TLS certificate valid for these names.

If neither of the above wildcard options is feasible, you have two choices:
# Serve web content at @collections.uuid_prefix.your.domain@, but only for unauthenticated requests (public data and collection sharing links). Authenticated requests will always result in file downloads, using the @download@ name. For example, the Workbench "preview" button and the "view entire log file" link will invoke file downloads instead of displaying content in the browser window.
# In the special case where you know you are immune to XSS exploits, you can enable the "trust all content" mode in Keep-web and Workbench (setting @Collections.TrustAllContent: true@ on the config file). With this enabled, inline web content can be served from a single @collections@ host name; no wildcard DNS or certificate is needed. Do not do this without understanding the security implications described in the "Keep-web documentation":http://godoc.org/github.com/curoverse/arvados/services/keep-web.

h2. Configure Keep-web

{% assign railscmd = "bundle exec ./script/get_anonymous_user_token.rb --get" %}
{% assign railsout = "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz" %}
If you intend to use Keep-web to serve public data to anonymous clients, configure it with an anonymous token. You can use the same one you used when you set up your Keepproxy server, or use the following command on the <strong>API server</strong> to create another. {% include 'install_rails_command' %}

Set the cluster config file like the following:

<notextile>
<pre><code>Clusters:
  <span class="userinput">uuid_prefix</span>:
    Services:
      Controller:
        ExternalURL: "https://<span class="userinput">uuid_prefix</span>.your.domain"
      WebDAV:
        InternalURLs:
          "http://keep_web_hostname_goes_here:9002/": {}
        ExternalURL: "https://collections.<span class="userinput">uuid_prefix</span>.your.domain"
      WebDAVDownload:
        InternalURLs:
          "http://keep_web_hostname_goes_here:9002/": {}
        ExternalURL: "https://download.<span class="userinput">uuid_prefix</span>.your.domain"
    Users:
      AnonymousUserToken: "{{railsout}}"
    Collections:
      TrustAllContent: false
    TLS:
      Insecure: false
</code></pre>
</notextile>

Set @Users.AnonymousUserToken: ""@ (empty string) if you do not want to serve public data.

Set @TLS.Insecure: true@ if your API server's TLS certificate is not signed by a recognized CA.

Workbench has features like "download file from collection" and "show image" which work better if the content is served by Keep-web rather than Workbench itself. We recommend using the two different hostnames ("download" and "collections" above) for file downloads and inline content respectively.

The following entry on your cluster configuration file (@/etc/arvados/config.yml@) details the URL that will be used for file downloads.

<notextile>
<pre><code>Clusters:
  <span class="userinput">uuid_prefix</span>:
    Services:
      WebDAVDownload:
        ExternalURL: "https://download.<span class="userinput">uuid_prefix</span>.your.domain"
</code></pre>
</notextile>

Additionally, one of the following entries on your cluster configuration file (depending on your DNS setup) tells Workbench which URL will be used to serve user content that can be displayed in the browser, like image previews and static HTML pages.

<notextile>
<pre><code>Clusters:
  <span class="userinput">uuid_prefix</span>:
    Services:
      WebDAV:
        ExternalURL: "https://*--collections.<span class="userinput">uuid_prefix</span>.your.domain"
        ExternalURL: "https://*.collections.<span class="userinput">uuid_prefix</span>.your.domain"
        ExternalURL: "https://collections.<span class="userinput">uuid_prefix</span>.your.domain"
</code></pre>
</notextile>

h2. Run Keep-web

h3. Start the service (option 1: systemd)

If your system does not use systemd, skip this section and follow the "runit instructions":#runit instead.

If your system uses systemd, the keep-web service should already be set up. Start it and check its status:

<notextile>
<pre><code>~$ <span class="userinput">sudo systemctl restart keep-web</span>
~$ <span class="userinput">sudo systemctl status keep-web</span>
&#x25cf; keep-web.service - Arvados Keep web gateway
   Loaded: loaded (/lib/systemd/system/keep-web.service; enabled)
   Active: active (running) since Sat 2019-08-10 10:33:21 UTC; 3 days ago
     Docs: https://doc.arvados.org/
 Main PID: 4242 (keep-web)
   CGroup: /system.slice/keep-web.service
           └─4242 /usr/bin/keep-web
[...]
</code></pre>
</notextile>

h3(#runit). Start the service (option 2: runit)

Install runit to supervise the Keep-web daemon.  {% include 'install_runit' %}

The basic command to start Keep-web in the service run script is:

<notextile>
<pre><code>exec keep-web
</code></pre>
</notextile>