Troubleshooting
Setup wizard
| Symptom | Cause | What to do |
|---|---|---|
| The wizard asks for the setup token again | This browser or tab never presented the token; the token lives in a cookie. | Paste the token again. This is expected in a new browser. |
| "The platform admin was not created" with a message about the setup token | An older UI didn't re-ask for the token in a new browser. | Upgrade, or verify the token again in this browser, then create the admin. |
| GitHub says the manifest's hook URL "isn't reachable over the public Internet" | Versions before 0.1.0-alpha.2 always put a webhook in the App manifest, and GitHub rejects localhost. | Upgrade. Current versions leave the webhook out when Infrared is opened on a local or private URL. |
| The sync step shows only wave 0 | Versions before 0.1.0-alpha.2 counted only the root Application. | Upgrade. Current versions show every Application the template creates. |
Argo CD
| Symptom | Cause | What to do |
|---|---|---|
The root Application shows ComparisonError mentioning the repo-server and connection refused | Argo CD's repo-server wasn't listening yet during the first sync. | Wait for the next sync, or force it: kubectl -n argocd annotate application <name> argocd.argoproj.io/refresh=hard --overwrite. |
infrared (wave 40) stays Unknown with "error pulling OCI chart" | Argo CD can't reach ghcr.io/darkshiftio/charts, or the repository entry argocd/infrared-charts is missing. | Check the cluster can reach ghcr.io, and that the Secret infrared-charts exists in argocd (template v0.1.1 and later create it). As a fallback, template v0.1.3 pulls the chart from its public git repo. |
infisical (wave 15) stays Progressing and its pod logs "Invalid environment variables" for AUTH_SECRET | Template versions before v0.1.2 generated empty Infisical keys. | Move to template v0.1.2 or later; the next sync repairs the Secret. Then restart Infisical: kubectl -n infisical rollout restart deploy. |
| A wave is Progressing for a long time | A chart is still pulling images or starting a database. | Look at the Application's resources in Argo CD, or kubectl get pods -A, for the pod that isn't Ready. |
Upgrades
| Symptom | Cause | What to do |
|---|---|---|
A helm upgrade you ran was undone | Argo CD manages Infrared after setup and reverts changes made outside the gitops repo. | Upgrade with a pin PR. See Upgrades. |
| Your edit to a gitops repo file disappeared after a template upgrade | The template owns that file and hydration overwrote it. | Keep your changes in files the template doesn't create. |