Secryn updates are delivered through the Self-Host Pro Docker registry. To pull updated images manually, you need a Docker access token from your Self-Host Pro product dashboard.

When You Need an Access Token

The install script handles authentication automatically during the initial setup. You only need to create an access token yourself if you want to:

• pull Secryn updates manually with Docker
• set up automated image updates on your server
• authenticate from a different Docker client or host

Create an Access Token

1. Go to app.selfhostpro.com/my-products
2. Sign in with the email used for your purchase
3. Open Secryn
4. Click Create Access Token
5. Copy the credentials shown on screen

You will receive:

• Username - your email address
• Token - the Docker registry password

The token is only shown once, so store it securely.

Log In to the Registry

Use your token to authenticate Docker against the Self-Host Pro registry:

docker login shpcr.io -u [email protected] -p your-token

To avoid storing the token in shell history, use stdin instead:

echo "your-token" | docker login shpcr.io -u [email protected] --password-stdin

Update Secryn

Pull the latest Secryn image:

docker pull shpcr.io/emrys/secryn:latest

Then restart the deployment from the installation directory:

cd /srv/secryn
docker compose up -d

Manage Tokens

From the Secryn product page in Self-Host Pro, you can manage existing access tokens.

Regenerate a Token

Regenerating creates a new token and immediately invalidates the old one.

1. Open Secryn in Self-Host Pro
2. Find the access token you want to replace
3. Click the three-dot menu
4. Select Regenerate
5. Copy the new token

Delete a Token

Deleting permanently removes the token. You will need to create a new one before Docker can authenticate again.

1. Open Secryn in Self-Host Pro
2. Find the access token you want to remove
3. Click the three-dot menu
4. Select Delete

Token Security

• access tokens grant pull access to all products tied to your account
• store tokens securely and never commit them to version control
• regenerate tokens immediately if you suspect exposure
• review the last-used timestamp in the dashboard to spot unused or unexpected tokens