Troubleshooting

Common issues and how to fix them.

"Command not found: rb"

pipx installed the CLI but didn't add it to your PATH.

Fix:

pipx ensurepath

Then restart your terminal (or run source ~/.bashrc / source ~/.zshrc).

On macOS with Homebrew-installed pipx, the binary is placed in ~/.local/bin. Verify it's in your PATH with echo $PATH.

"Authorization required" / 401 errors

Your access token has expired. Access tokens last 1 hour and should auto-refresh, but sometimes the refresh fails.

Fix:

rb auth login

This opens the browser for a fresh authentication. If the problem persists, check your internet connection and ensure razorbridge.eu is reachable.

"Connection refused" when using rb blade ssh

The blade might not be ready yet, or it may have been torn down.

Fix:

rb blade status

If status is provisioning — the blade is still starting up. Wait 1-2 minutes and try again.
If status is running — try again in 30 seconds. The SSH daemon may still be initializing.
If status is stopped or terminated — the event has ended or the blade was reclaimed.

Can't connect via VS Code Remote-SSH

VS Code needs an SSH config entry to find your blade.

Fix:

Run rb blade config --append to write the SSH config entry.
In VS Code, press Cmd+Shift+P (or Ctrl+Shift+P) and type “Remote-SSH: Connect to Host”.
Select your blade from the list (e.g., gpu-blade-abc123).

Ensure the blade is still running (rb blade status). If the blade was restarted, run rb blade config --append again — the IP or credentials may have changed.

File transfer issues on Windows

File transfer uses the system's scp/rsync binary (via the SSH config alias from rb blade config), which is not available natively on Windows.

Fix:

Recommended: Install WSL (Windows Subsystem for Linux) and run scp/rsync from your WSL terminal.
Alternative: Install OpenSSH for Windows (included in Windows 10 1803+). Open Settings > Apps > Optional Features > Add OpenSSH Client.

"Insufficient credits" / 402 error

Your credit balance is too low for the requested operation.

Fix:

$ rb credits
Balance: €0.12
  ⚠ Low balance — some operations may be blocked.

If you're a student — contact your professor or organization admin. They can grant credits from their balance.
If you're an organizer — contact KlusAI at [email protected] to request a credit grant.

Blade disconnected unexpectedly

The blade may have crashed or been recovered by the platform.

Fix:

rb blade status

If status shows recovered — the blade was restarted. Run rb blade ssh again. You will get new SSH credentials, but your files on disk are preserved.
If status shows failed — the blade could not be recovered. Contact your event organizer. Your work may be lost if not downloaded.
If status shows running — it may have been a network hiccup. Try rb blade ssh again.

Download important results regularly with scp or rsync (e.g. rsync -avP gpu-blade-<id>:~/outputs/ ./outputs/). Don't wait until the last minute before event teardown.

"Event not found" when joining

The join code doesn't match any active event.

Fix:

Check the code spelling — codes are case-insensitive and follow the format XXXX-YYYY (e.g., CUDA-2026).
Ask your professor or organizer for the correct code.
The event may not have started yet or may have already ended. Check with the organizer.

Still stuck?

If none of the above solved your issue:

Run rb doctor to check your local environment
Contact your event organizer for event-specific issues
Email [email protected] for platform issues