# WordPress Migration Failure - seedvault.market

**Date:** May 22, 2026  
**Site:** seedvault.market  
**Status:** Content lost due to migration error

---

## What Went Wrong

### The Critical Error
**I told the user to change DNS to the new NUC server BEFORE backing up the old WordPress.com site.**

This is backwards. The correct migration order is:
1. ✅ Backup old site
2. ✅ Set up new environment
3. ✅ Migrate content
4. ❌ Change DNS (done first - wrong)

### Timeline of Failure

1. **NUC Setup Completed**
   - Docker containers running (WordPress + MySQL)
   - Nginx reverse proxy configured
   - SSL certificate obtained (Let's Encrypt)
   - WordPress installed and accessible at `https://seedvault.market`

2. **DNS Changed Prematurely**
   - User changed DNS A records from WordPress.com to NUC IP (`71.227.20.51`)
   - WordPress.com detected external hosting and auto-disconnected the site
   - Site disappeared from WordPress.com dashboard

3. **No Backup Existed**
   - User had not exported WordPress.com content before DNS change
   - I should have insisted on backup before DNS change
   - No XML export, no All-in-One WP Migration backup

4. **Content Lost**
   - WordPress.com site disconnected/suspended
   - Domain removed from WordPress.com account
   - All posts, pages, products, media inaccessible
   - No local backups to restore from

---

## What Was Working

### NUC Configuration (Still Functional)
```
Docker Containers:
- seedvault-wordpress-1 (WordPress, port 8081→80)
- seedvault-db-1 (MySQL, port 3306)

Nginx:
- Reverse proxy on ports 80/443
- SSL certificate valid (Let's Encrypt)
- Proxy to localhost:8081

Database:
- WordPress configured for https://seedvault.market
- Database: wordpress
- All URLs corrected (was pointing to 127.0.0.1:8081)
```

### What Was Fixed
- WordPress `home` and `siteurl` updated from `http://127.0.0.1:8081` to `https://seedvault.market`
- External access working (no more port 8081 redirect)
- SSL certificate valid

---

## Recovery Options Attempted

### 1. WordPress.com Support (Recommended)
- Status: Not yet attempted
- URL: https://wordpress.com/support/contact/
- Request: Site restoration or full XML export
- Chance: Low but worth trying

### 2. DNS Reversion (In Progress)
- Pointing DNS back to WordPress.com (`192.0.78.24`)
- Hope WordPress.com auto-reconnects site
- Can then export immediately

### 3. Rebuild from Scratch
- Install WooCommerce on NUC WordPress
- Rebuild ~32 products manually or via CSV
- Last resort if recovery fails

---

## Lessons Learned

### Never Do This Again

**Migration Order (Correct):**
1. **BACKUP FIRST** - Export WordPress.com site (XML or All-in-One WP Migration)
2. Set up new environment (NUC, Docker, Nginx, SSL)
3. Test new environment locally (internal IP, not public domain)
4. Migrate content to new environment
5. **THEN change DNS** - Point domain to new server
6. Verify everything works on new server
7. Keep old site running until confirmed migration success

**Critical Rules:**
- ✅ Always backup before any DNS change
- ✅ Test new environment on internal IP first
- ✅ Keep old site running until migration verified
- ✅ Have rollback plan before making changes

### What I Should Have Done

1. **Insisted on backup before DNS change**
   - This is non-negotiable in any migration
   - I told user to change DNS first - wrong

2. **Tested on internal IP first**
   - NUC should have been tested on `http://192.168.1.100:8081`
   - No DNS change needed for initial testing
   - Would have caught issues before going live

3. **Created rollback plan**
   - Should have documented how to revert DNS if needed
   - Should have warned about WordPress.com auto-disconnection

4. **Verified WordPress.com behavior**
   - Should have known WordPress.com disconnects sites on DNS change
   - This is documented WordPress.com behavior

---

## Current Status (May 22, 2026)

- **NUC WordPress:** Working, empty, accessible at https://seedvault.market
- **WordPress.com Site:** Disconnected, inaccessible, possibly deleted
- **Content:** Lost (no backup exists)
- **DNS:** Being reverted to WordPress.com to attempt recovery

---

## Action Items

1. ✅ DNS A records pointing to WordPress.com (`192.0.78.24`)
2. ⏳ Wait for DNS propagation (15-60 minutes)
3. ⏳ Check if WordPress.com auto-reconnects site
4. ⏳ If site appears, export immediately (Tools → Export)
5. ⏳ If site doesn't appear, contact WordPress.com support
6. ⏳ If support fails, rebuild store on NUC

---

## Post-Mortem

**Root Cause:** Bad migration instructions from me. Told user to change DNS before backing up.

**Impact:** Complete loss of WordPress.com site content (posts, pages, products, media).

**Prevention:** 
- Always backup before DNS changes
- Test new environment on internal IP first
- Document rollback procedures
- Verify hosting provider behavior before migration

**Owner:** Vincent (Hermes AI)

---

*This document exists to ensure this mistake is never repeated.*