When you switch Bluesky accounts to a different Personal Data Server PDS, you may see a “Repository Not Found” error. This error means the new PDS cannot locate the account’s data repository. The repository is the storage location for your posts, follows, and profile on the AT Protocol. This article explains why the error occurs and provides step-by-step instructions to fix it.
Key Takeaways: Fixing the Bluesky PDS Switch Error
- Settings > Account > Switch PDS: Use this menu to initiate the PDS change and avoid manual configuration mistakes.
- Account migration via Bluesky’s official tool: The only supported method to transfer your repository to a new PDS without data loss.
- Manual DNS record update: Required for custom domain handles after switching PDS to restore verification.
Why Bluesky Shows ‘Repository Not Found’ After PDS Switch
Bluesky uses the AT Protocol, where each account has a unique repository on a PDS. When you switch to a new PDS, the old repository does not automatically move. The new PDS looks for your account’s repository in its own storage and cannot find it. The error appears because the account’s DID decentralized identifier still points to the old PDS, but the new PDS has no data for that DID.
The root cause is that a PDS switch without a proper migration leaves the account in a half-migrated state. The Bluesky app tries to fetch your data from the new PDS, but the repository never arrived there. This can happen if you manually changed the PDS endpoint in the app settings or if a third-party tool performed an incomplete migration.
What the Error Message Means
The exact text reads: “Repository not found” or “Could not locate repository for DID.” This confirms the new PDS has no record of your account’s data. The error does not mean your account is deleted. Your data still exists on the original PDS until you complete a proper migration.
Steps to Fix the Repository Not Found Error
Follow these steps in order. Do not skip any step. If one method fails, proceed to the next.
Method 1: Revert to the Original PDS
- Open Bluesky Settings
Tap the menu icon three lines in the top-left corner. Select Settings from the bottom of the menu. - Go to Account Settings
In the Settings page, tap Account. This opens your account details and PDS information. - Locate the Current PDS Endpoint
Scroll to the bottom of Account settings. Look for “Personal Data Server” or “PDS Endpoint.” It shows a URL like https://old-pds.example.com. - Switch Back to the Original PDS
Tap the PDS endpoint field. Enter the original PDS URL that worked before the switch. Tap Save or Confirm. The app will restart and attempt to load your data from the original server. - Wait for Account Recovery
After switching back, the app fetches your repository from the original PDS. This may take up to 30 seconds. If the error disappears, your account is restored on the original PDS. Do not switch again without a proper migration.
Method 2: Perform a Proper Account Migration
If reverting is not possible or you want to stay on the new PDS, you must migrate your repository. Bluesky provides an official migration tool for this.
- Access the Migration Tool
Open a web browser on your computer. Go to the Bluesky account migration page at https://bsky.social/settings/migration. Sign in with your Bluesky credentials. - Select the Target PDS
On the migration page, you see a list of available PDS servers. Choose the new PDS you want to use. If your PDS is self-hosted, enter its URL manually. - Initiate the Migration
Click Start Migration. The tool copies your entire repository — posts, follows, likes, and profile — from the original PDS to the new one. This process can take several minutes depending on the size of your account. - Verify Migration Completion
After the migration finishes, the page shows a success message. Open the Bluesky app and go to Settings > Account. The PDS endpoint should now display the new server URL. Your feed and profile should load normally. - Update Your DNS Records for Custom Domains
If you use a custom domain as your handle, you must update the DNS TXT record. Go to your domain registrar’s DNS settings. Find the TXT record for _atproto.yourdomain.com. Change the value to the new PDS endpoint. Save the record and wait for DNS propagation, which can take up to 24 hours.
Method 3: Create a Fresh Account on the New PDS
Use this method only if the migration fails or you do not need your old data.
- Log Out of Your Current Account
In the Bluesky app, go to Settings > Account > Sign Out. Confirm the sign-out. - Clear App Data
On iOS, go to Settings > General > iPhone Storage > Bluesky > Delete App. Reinstall Bluesky from the App Store. On Android, go to Settings > Apps > Bluesky > Storage > Clear Data. On Windows or Mac, uninstall the app and reinstall it from the official website. - Create a New Account
Open the app. Tap Create New Account. When prompted to choose a server, select the new PDS from the list. If your PDS is not listed, tap Other and enter the PDS URL. Complete the signup process with a new handle and password. - Verify the New Account Works
After creation, the app loads an empty account. The “Repository Not Found” error should not appear because the new PDS created a fresh repository for you. Your old data is not recoverable through this method.
If Bluesky Still Has Issues After the Main Fix
Error Persists After Reverting to Original PDS
If the error continues after reverting, the original PDS may be down or unreachable. Check the status of your original PDS by visiting its health endpoint, usually at https://original-pds-url.com/xrpc/_health. If the PDS is offline, wait for the server administrator to restore it. Contact your PDS provider for an estimated recovery time.
Migration Tool Shows ‘Repository Locked’
This occurs when another migration is already in progress. Wait 15 minutes and try again. If the issue persists, sign out of all Bluesky sessions on other devices and browsers. Then repeat the migration steps.
Custom Domain Handle Not Verified After Switch
Your custom domain handle shows a red warning triangle. This means the DNS TXT record still points to the old PDS. Update the record as described in Method 2, step 5. Use a DNS checker tool like whatsmydns.net to confirm propagation. Once the DNS change propagates, the handle verifies automatically.
Comparison of PDS Switch Methods
| Item | Revert to Original PDS | Official Migration Tool | Create Fresh Account |
|---|---|---|---|
| Data preserved | All data on original PDS | All data moved to new PDS | No old data kept |
| Time required | Less than 5 minutes | 5 to 30 minutes | 10 minutes |
| Custom domain handle | No DNS change needed | DNS record update required | DNS record update required |
| Risk of data loss | None | Low if migration completes | High — loses all old data |
After resolving the error, test your account by posting a short message and refreshing your feed. If you used the migration tool, verify that your follower count and post history are intact. For future PDS switches, always use the official migration tool to avoid the “Repository Not Found” error. Consider backing up your account data using the export feature in Settings > Account > Export Data before any PDS change.