✅ Quick Summary
Match the error message you're seeing to the fixes below. Most Push44 errors are caused by credentials, not by Push44 itself, so re-checking your tokens resolves the vast majority of failures.
The Problem
Exports can fail for a handful of predictable reasons: an expired or malformed token, a sleeping platform container, insufficient GitHub permissions, or hitting an API rate limit. Without knowing what each error means, it's easy to get stuck.
How Push44 Solves It
Match the error message you're seeing to the fixes below. Most Push44 errors are caused by credentials, not by Push44 itself, so re-checking your tokens resolves the vast majority of failures.
Step-by-Step Guide
"401 Unauthorized" or "Bad credentials"
Your platform token or GitHub token has expired or was typed incorrectly. Regenerate the token from the platform's settings page and re-paste it into Push44 — don't reuse an old token from clipboard history.
"404 Not Found" on GitHub push
The repository name doesn't exist and Push44 couldn't create it, usually because your GitHub PAT is missing the 'repo' scope. Regenerate your token at github.com/settings/tokens with the full 'repo' scope checked.
"Container is sleeping" (Rocket.new)
Rocket.new puts inactive project containers to sleep. Open the project directly in Rocket.new's editor to wake it, wait about 15 seconds, then retry the export in Push44.
"Rate limit exceeded"
GitHub's API allows 5,000 authenticated requests per hour. This is rarely hit by normal use, but if you're exporting very large projects repeatedly, wait an hour or use a token with a higher rate limit tier.
"Session expired" (Floot or Zite)
Session-based tokens (Floot, Zite) expire after a period of inactivity. Log back into the platform in your browser, copy a fresh session cookie value, and update it in Push44's credentials screen.
Pro Tips
- Copy tokens directly — never retype them by hand, as a single wrong character causes silent auth failures.
- If an export fails midway, no partial commit is created — GitHub Trees API pushes are atomic, so your repo is never left in a broken state.
- Check the browser console (F12) for the raw API error if Push44's message isn't specific enough.
Common Mistakes to Avoid
- Assuming a failed export means data loss — Push44 never writes anything until the full commit is ready.
- Retrying immediately without fixing the underlying token issue — this just repeats the same error.
- Using a fine-grained GitHub PAT without repository access explicitly granted to the target repo.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.