To run the Snap Store Proxy, you will need:

  • A server running Ubuntu 16.04 LTS on AMD64.
  • The ability (e.g. firewall rules) for the server to initiate network connections to,, and
  • A domain name for the server.
  • A PostgreSQL instance, and credentials for a user with CREATEROLE privileges, and either CREATEDB or a pre-created database with CREATE privileges on it for that user. The snap-store-proxy snap will create "snapauth" and "snaprevs" users, so you will need to ensure that any relevant ACLs permit those.
  • An RSA key pair to register the snap-store-proxy identity (these can be generated for you with: snap-proxy generate-keys).

Getting started

First, if your network requires an HTTPS proxy to get to the above domains, you must first configure snapd on the installation server to use that HTTPS proxy in order to be able to install the snap-store-proxy snap package.

Do this by adding the appropriate environment variables (http_proxy, https_proxy) to the server’s /etc/environment file, and restarting snapd:

sudo systemctl restart snapd

Installing the stable release of the Snap Store Proxy is as simple as:

sudo snap install snap-store-proxy

This will install the snap, which provides a collection of systemd services, and the snap-proxy CLI tool to control the proxy.

Domain configuration

The Snap Store Proxy will require a domain or IP address to be set for the configuration and access by other devices.

sudo snap-proxy config proxy.domain="<domain>"

This can be done after the database is created, but is required before registration can succeed.

The proxy will listen on all interfaces on port 443 (with a redirect from 80).


To initially configure the Snap Store Proxy, you will need either a database already prepared, or a connection string with a user with CREATEDB permissions.

Prepared database

A prepared database must have the btree_gist extension installed. This extension requires superuser privileges to create.

If the database is already prepared, set the connection string.

sudo snap-proxy config \

This will require a user with CREATEROLE permission but does not require CREATEDB permissions.

The connection string behaves as per normal PostgreSQL clients. i.e. USER will default to 'root', HOST defaults to 'localhost', PGPORT defaults to '5432', DBNAME defaults to USER.

Creating a database

There is a convenience option that will create and configure the database automatically.

The create-database command can create a database with a connection string including a user that has the appropriate permissions (CREATEDB).

sudo snap-proxy create-database \

The connection string behaves as per normal PostgreSQL clients. i.e. USER will default to 'root', HOST defaults to 'localhost', PGPORT defaults to '5432', DBNAME defaults to USER. The PASSWORD here is optional, and if needed will be prompted for by the command (to avoid leaving credentials in your shell's history).

This will create and migrate the database.

Network connectivity

You can check that the Proxy can access all the network locations it needs to with:

snap-proxy check-connections

If you require an HTTPS proxy, you can configure the proxy to use that with:

sudo snap-proxy config proxy.https.proxy=myproxy.internal:3128

Next step

With the domain set, and database configured your proxy should now be ready to be registered.

Running multiple proxies

You can run multiple instances of the proxy for HA, provided by simple round-robin DNS. All instances need to have the same configuration, using your normal configuration managment system. Once a key pair has been registered, it will not need registering on other instances.

Note: The download caching will currently be less efficient when running multiple instances, as the instances are not aware of each other. Support for shared caching is planned for later releases of the Snap Store Proxy.