Below are a few issues you might encounter while working with API Signer, along with their workarounds.
Are you seeing output like this?
Post "https://api.fordefi.com/api/v1/logs": oauth2: cannot fetch token: 401 Unauthorized
Response: {"title":"User is not authorized","detail":"failed to authorize api signer","request_id":"fe17407d-2372-9baf-85e6-447dfeb1b919"}This error usually indicates a stale or misconfigured API Signer setup.
To resolve the issue, remove the existing Signer — including its Docker volume and configuration — and perform a fresh setup:
Check which Docker volume the Signer is using (the default is
vol):docker volume lsRemove the volume:
docker volume rm <volume_name>Delete the old Docker config file:
rm ~/.docker/config.jsonSkip this step if you're running multiple API Signers for different Fordefi workspaces on the same host. This file is global, so deleting it would also affect your other healthy API Signers.
Remove the API Signer from the Fordefi web console:
Navigate to Settings > API Signer in the Fordefi web console and delete the existing Signer.

Set up a new API Signer by following the instructions here: Set up an API Signer
To upgrade your Signer to the latest version:
Stop the currently running API Signer container.
Log in to Fordefi’s Artifactory and pull the latest image:
docker login -u fordefi fordefi.jfrog.ioRetrieve your password by navigating to Settings > API Signer, then clicking View Docker Credentials.
docker pull fordefi.jfrog.io/fordefi/api-signer:latestRestart the API Signer container.
Call this endpoint to retrieve the latest versioned image:
curl -s -u username:password "https://fordefi.jfrog.io/artifactory/api/docker/fordefi/v2/api-signer/tags/list" | jq -r '.tags[]' | grep "^v" | sort -V | tail -1Pull and install that specific version:
docker pull --platform linux/amd64 fordefi.jfrog.io/fordefi/api-signer:v0.105.39Run the command from step 1 periodically to check whether a newer version is available.