Repository navigation
FAQ
- What is Warracker?
- What do I need to run it?
- Can I use SQLite or another database instead of PostgreSQL?
- Can I run Warracker without Docker?
- Where is my data?
- Is there a mobile app?
- How many users can I have?
- How do I disable registration after my users are created?
- Can I share my warranties with other users, like my family?
- I forgot my password. How do I get back in?
- OIDC sign-in redirects to localhost, or fails — what should I check?
- Can I serve Warracker under a subpath, like example.com/warracker?
- Can each user connect their own Paperless-ngx account?
- Does deleting a warranty or claim delete my documents from Paperless-ngx?
- Can I export everything, files included, as one archive?
- My CSV import fails or imports nothing — what does the file need?
- Can I set the expiration date directly instead of a duration?
- What happens on the day a warranty expires?
- Do expiry notifications repeat?
- Does Warracker handle multiple currencies?
- How do I update Warracker?
- How do I report a bug or request a feature?
Warracker is an open-source, self-hosted warranty tracker. It organizes product warranties, monitors expiration dates, and stores receipts, invoices, manuals, and other documents in one place. See Home for the feature list.
Docker and Docker Compose. The compose file includes PostgreSQL, so you do not need a separate database server. See Getting Started.
No. Warracker requires PostgreSQL — the compose file runs one for you, and there is no embedded-database mode. If you already run PostgreSQL elsewhere, point the DB_* variables at it instead (see Configuration).
Yes, from source, but Docker is the supported install. From source you need Python, a PostgreSQL server, and to run the database migrations yourself (backend/migrations/apply_migrations.py), then serve the static frontend files and run the backend with Gunicorn. The Docker image does all of that for you on startup.
On your own server: warranties and users live in PostgreSQL, uploaded files live in the uploads volume (/data/uploads inside the container). Your warranty data is not sent anywhere. The only outbound call is the About page checking GitHub for a newer release.
No native app. The web interface is responsive and works on phones and tablets, and it is installable as a progressive web app (PWA): use your browser's "Add to Home Screen" / "Install" option to get an app-like icon.
There is no hard limit. The first account created on a fresh install automatically becomes the owner/admin. See Authentication for roles and the global view.
An admin can turn registration off in the admin site settings (the registration toggle in Settings). Existing accounts are unaffected; new sign-ups are refused. See Security for the recommended setup.
Yes — that is what the global view is for. When it is on (it is by default), every signed-in user on the instance can browse all warranties, including invoices, manuals, and product photos. "Other documents" and claim documents stay visible to the owner and admins only. Admins can turn the global view off, or limit it to admins, in the site settings. See Authentication.
Use the "Forgot password" link on the login page. That sends a reset link by email, so it only works if SMTP is configured (see Configuration). An admin cannot reset another user's password from the admin panel, so keep a second admin account as a backup — see Security.
Almost always the public URL. Warracker builds the OIDC redirect address from the URL it believes it lives at, so the frontend URL in Configuration must be your real public address — including the port, if it is non-standard — not localhost. If the identity provider itself cannot be reached, check the server's network path to it as well. Authentication and Troubleshooting walk through the common cases.
Not currently. Warracker must be served at the root of a domain (for example, warracker.example.com). Subpath support is an open feature request. See Reverse Proxy for root-domain examples.
Not yet. Paperless-ngx is configured once for the whole instance, and document access is then tracked per Warracker user (see Paperless-ngx). Per-user Paperless tokens are an open feature request.
No. Warracker never deletes anything from Paperless-ngx. Deleting a warranty or a claim removes Warracker's link to the document and deletes files stored locally in Warracker, but the document itself stays in Paperless-ngx untouched.
Not yet. CSV export covers all warranty data but not the uploaded files. A full backup is a database dump plus a copy of the uploads folder — see Backup and Restore. A single-archive export is an open feature request.
The required columns are ProductName and PurchaseDate in ISO format (YYYY-MM-DD), plus a duration (years, months, or days) — unless the row is a lifetime warranty or gives an ExpirationDate instead. A file exported from Warracker always re-imports cleanly. The full field reference is in the User Guide.
Yes. The add and edit forms accept either a duration — years, months, and days in any combination — or an exact expiration date; use whichever the paperwork states. Lifetime warranties have no expiration date at all. CSV import accepts an ExpirationDate column the same way.
The warranty is still active until the end of the expiry date. It flips to Expired the following day.
No. Each notification is sent once per threshold per warranty per channel. If you set thresholds of 7 and 30 days, you get one notification at each threshold, not daily reminders. See Notifications.
Yes. Each warranty has its own currency. The status dashboard's Total Value counts warranties in your settings currency plus warranties saved with no currency; warranties in a different currency are excluded by design.
See Updating. Short version: back up, pull the new image, recreate the container — database migrations run automatically on startup.
Open an issue on GitHub and include:
- The Warracker version (shown on the About page)
- How you installed it (Docker Compose, Unraid, from source)
- Steps to reproduce the problem
- Relevant lines from
docker compose logs warracker
For security vulnerabilities, do not open a public issue — use GitHub's private vulnerability reporting on the repository instead. See Security.