API Signer: Troubleshooting

Following are a few issues that might present themselves while you work wih API Signer, with 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. Here are the steps to perform:

1. Check which Docker volume the Signer is using (default is vol):

   docker volume ls

2. Remove the volume:

   docker volume rm <volume_name>

3. Delete the old Docker config file:

   rm ~/.docker/config.json

4. Remove the API Signer from the Fordefi web console:

   Navigate to Settings > API Signer in the Fordefi web console and delete the existing Signer.

   

5. Set up a new API Signer by following the instructions here:
   Set up an API Signer

To upgrade your Signer to the latest version:

1. Stop the API Signer container that is currently running.

2. Log in to Fordefi’s Artifactory and pull the latest image:

   docker login -u fordefi fordefi.jfrog.io

   Retrieve your password by clicking: Settings > API Signer, then click View Docker Credentials.

   docker pull fordefi.jfrog.io/fordefi/api-signer:latest

3. Restart the API Signer container.

1. Call this endpoint, which returns 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 -1

2. Pull and install that specific version:

   docker pull --platform linux/amd64 fordefi.jfrog.io/fordefi/api-signer:v0.105.39`

3. Run the command in step 1 from time to time to check if a later version is available.