Skip to content

Troubleshooting

Jump to bottom
SamsterZero edited this page Aug 11, 2026 · 3 revisions

Troubleshooting

First checks

  1. Run docker compose ps or podman compose ps with the same project and Compose file used to start Prizen.
  2. Inspect logs with docker compose logs or podman compose logs.
  3. Confirm http://127.0.0.1:3000/api/health returns {"status":"ok"}.
  4. Confirm pgdata and prizen_secrets still exist.
  5. Confirm the Compose file and PRIZEN_IMAGE use the same release version.

Builds that include it also provide the Operations-Dashboard for a sanitized view of tracker, scan queue, notification, storage, and backup health.

Podman provider cannot connect

podman compose may delegate to Docker Compose. The provider notice is normal, but it needs the rootless Podman API socket:

systemctl --user enable --now podman.socket

Registry or DNS errors

For errors mentioning registry-1.docker.io or name resolution, verify DNS before retrying:

getent hosts registry-1.docker.io

Do not use --pull=never after deleting images; the required Bun, PostgreSQL, and Prizen images must exist locally first.

Stale local source image

An error such as Module not found scripts/init-secrets.ts means the local image does not match the current source. Rebuild it, then recreate the stack:

podman build -t docker.io/library/prizen:local .
PRIZEN_IMAGE=docker.io/library/prizen:local podman compose -p prizen-source \
  -f compose.release.yaml up -d --wait --force-recreate

Port already in use

Check the listener with ss -ltn '( sport = :3000 )'. Start Prizen on another loopback port:

PRIZEN_PORT=3001 ORIGIN=http://localhost:3001 \
  PRIZEN_IMAGE=docker.io/library/prizen:local \
  podman compose -p prizen-source -f compose.release.yaml up -d --wait

Fresh reset

Deleting images or containers does not delete named volumes. To permanently remove only the chosen Prizen Compose project's database and generated secrets:

podman compose -p prizen-source -f compose.release.yaml down --volumes

This cannot be undone without a backup. Omit --volumes during normal stops and updates.

Amazon challenge pages, markup changes, throttling, and invalid Creators API eligibility are marketplace failures rather than container-health failures.

Report reproducible defects in GitHub Issues. Report vulnerabilities privately using the security policy.

Prizen

Clone this wiki locally