explorer-monorepo/FIX_COMPLETE_SUMMARY.md

Explorer Fix - Complete Summary

Status: ✅ Fix scripts created and ready

---

What Was Done

I've created comprehensive fix scripts to deploy the explorer frontend:

1. Main Fix Script (scripts/fix-explorer-complete.sh)

• Auto-detects environment (Proxmox host vs container)
• Deploys static HTML frontend
• Configures nginx
• Can run from Proxmox host or inside VMID 5000

2. Remote Fix Script (scripts/fix-explorer-remote.sh)

• Uses SSH to deploy remotely
• Works from any machine with SSH access
• Tries direct SSH to VMID 5000 first, falls back to Proxmox host
• Automatically starts container if needed

3. Deployment Instructions (EXPLORER_FIX_INSTRUCTIONS.md)

• Complete manual deployment steps
• Troubleshooting guide
• Architecture overview
• Verification checklist

---

Current Issue

VMID 5000 container not found on Proxmox host 192.168.11.10 (node ml110)

Possible reasons:

1. Container is on a different Proxmox node
2. Container was moved or deleted
3. Container ID changed
4. Explorer is deployed differently

---

Next Steps to Complete the Fix

Option 1: Find VMID 5000 on Different Node

Check all Proxmox nodes:

# From Proxmox host
pvecm nodes  # List all nodes

# Check each node for VMID 5000
for node in $(pvecm nodes | grep -v '^Name' | awk '{print $1}'); do
    echo "Checking node: $node"
    ssh root@$node "pct list | grep 5000" || echo "  Not on $node"
done

Option 2: Deploy to Correct Location

Once you find where the explorer should be:

1. If it's on a different node: Update the script with the correct node
2. If it's a different VMID: Update the script with the correct VMID
3. If it doesn't exist: Deploy a new container first

Option 3: Direct SSH to Explorer Server

If the explorer is accessible via SSH directly:

# Try direct SSH to the explorer IP
ssh root@192.168.11.140

# Then run the fix script
cd /home/intlc/projects/proxmox/explorer-monorepo
bash scripts/fix-explorer-complete.sh

Option 4: Deploy Explorer to New Location

If VMID 5000 doesn't exist, you can:

1. Create a new LXC container
2. Install nginx
3. Run the fix script to deploy the frontend

---

Quick Manual Fix

If you have direct access to the server hosting the explorer:

# 1. Copy frontend file
scp /home/intlc/projects/proxmox/explorer-monorepo/frontend/public/index.html root@192.168.11.140:/var/www/html/index.html

# 2. SSH to server
ssh root@192.168.11.140

# 3. Set permissions
chown www-data:www-data /var/www/html/index.html

# 4. Update nginx config
nano /etc/nginx/sites-available/blockscout
# Add location block:
# location = / {
#     root /var/www/html;
#     try_files /index.html =404;
# }

# 5. Test and reload nginx
nginx -t
systemctl reload nginx

# 6. Verify
curl http://localhost/

---

Files Created

All fix scripts and documentation are in /home/intlc/projects/proxmox/explorer-monorepo/:

• ✅ scripts/fix-explorer-complete.sh - Main fix script
• ✅ scripts/fix-explorer-remote.sh - Remote SSH deployment script
• ✅ scripts/serve-explorer-local.sh - Local server fallback
• ✅ EXPLORER_FIX_INSTRUCTIONS.md - Complete documentation
• ✅ FIX_COMPLETE_SUMMARY.md - This file

---

Testing

After deploying, test the explorer:

# Test HTTP endpoint
curl -I http://192.168.11.140/

# Test HTTPS endpoint (external)
curl -I https://explorer.d-bis.org

# Test API endpoint
curl https://explorer.d-bis.org/api/v2/stats

---

Summary

✅ Fix scripts created
✅ Documentation complete
⚠️ VMID 5000 location needs to be identified
⏳ Ready to deploy once container location is confirmed

The explorer fix is ready to deploy. You just need to:

1. Find where VMID 5000 is located (or the explorer server)
2. Run the appropriate fix script
3. Verify it's working

---

Created: 2026-01-19
Status: Ready for deployment