Rollback & history

Inspect past deployments and restore a known-good release.

Who can use this page? Site managers with Git Deployment on the site.

Open history

Site Actions → Git Deployment → deployment history (wording may be Deployments / history list).

Each entry shows:

• Commit SHA / message
• Status (building, healthy, failed, rolled back)
• Timestamp
• Logs

Automatic rollback

If the new release fails its health check during activation:

1. NitHost restores the previous Git release
2. Or the original manual runtime if this was the first deployment
3. History records the failure

Manual rollback

1. Open deployment history
2. Select a successful past deployment
3. Choose Rollback (restore that release)
4. Confirm — the retained release is re-activated

Only retained successful releases can be selected. Contact NitHost support if the release you need is no longer available.

When to roll back

• Bad migration or build flag
• Health path passing in CI but failing in production
• Dependency that breaks at runtime after activation

Rollback restores code/release, not necessarily database schema. Keep migrations backward-compatible for one release, or restore DB from backup deliberately.

Related

• Connect a repository
• Backups & restore