tweets-2-bsky#

A powerful tool to crosspost Tweets to Bluesky, supporting threads, videos, and high-quality images.

Troubleshooting#

Update Failures / Git Conflicts#

If ./update.sh fails with "Pulling is not possible because you have unmerged files" or similar git errors:

Reset your local repository to match the remote (Warning: this discards local changes to tracked files):
```
git reset --hard origin/master
```
Run the update script again:
```
./update.sh
```

PM2 interpreter mismatch#

If PM2 logs show command/runtime errors after an update (for example stale interpreter paths):

Common error signature:

TypeError: require() async module ".../dist/index.js" is unsupported. use "await import()" instead.

Run the repair script:
```
chmod +x repair_pm2.sh
./repair_pm2.sh
```

If needed, manually recreate PM2 with Bun as the process command:

pm2 delete tweets-2-bsky || true
pm2 delete twitter-mirror || true
pm2 start "$HOME/.bun/bin/bun" --name tweets-2-bsky --cwd "$PWD" -- dist/index.js
pm2 save

Old crash lines remain in PM2 logs until log rotation/flush. Clear them if needed:
```
pm2 flush
```

`bun: command not found`#

If Bun is missing on a source install host:

Run either installer/updater once (they auto-install and auto-upgrade Bun to latest stable):
```
./install.sh --no-start
# or
./update.sh --no-restart
```

Native module load failure (`ERR_DLOPEN_FAILED`)#

If startup fails while loading native dependencies:

Reinstall/rebuild native dependencies with Bun:
```
bun run rebuild:native
```
Rebuild and start:
```
bun run build
bun run start
```

Dashboard appears unstyled / plain text UI#

If the app loads but looks mostly unstyled:

Rebuild web assets:
```
bun run build
```
Restart server:
```
bun run start
```
Hard refresh browser cache (Cmd+Shift+R on macOS).

CLI command not recognized#

When using Bun scripts, pass CLI args after --:

bun run cli -- status

Scheduler appears stuck on one account#

If a single source account hangs for a long time (media fetch/processing), scheduled checks now skip that account after a timeout and continue with the next one.

Default timeout: 480000 ms (8 minutes)
Override with env var: SCHEDULED_ACCOUNT_TIMEOUT_MS

Examples:

# Docker
docker run -d --name tweets-2-bsky -e SCHEDULED_ACCOUNT_TIMEOUT_MS=300000 -p 3000:3000 -v tweets2bsky_data:/app/data j4ckxyz/tweets-2-bsky:latest

# Source install (.env)
echo 'SCHEDULED_ACCOUNT_TIMEOUT_MS=300000' >> .env
./update.sh

To watch logs while debugging on Raspberry Pi:

docker logs -f tweets-2-bsky
# or for source/PM2
pm2 logs tweets-2-bsky

Docker: permissions writing `/app/data`#

If the container fails to write config.json or database.sqlite, ensure /app/data is writable by the container process.

For easiest portability, use a named Docker volume:

docker volume create tweets2bsky_data
docker run -d --name tweets-2-bsky -p 3000:3000 -v tweets2bsky_data:/app/data ghcr.io/j4ckxyz/tweets-2-bsky:latest

The container stores persistent state under TWEETS2BSKY_DATA_DIR (default /app/data). If you mount a different path, set that env var to match:

docker run -d --name tweets-2-bsky -p 3000:3000 -v /host/path:/persist -e TWEETS2BSKY_DATA_DIR=/persist ghcr.io/j4ckxyz/tweets-2-bsky:latest

Docker: updating image#

In Docker mode, update by pulling a newer image and recreating the container with the same volume. /api/update / update.sh are source-install workflows.

Configure Feed