# Fix All Issues — Single Runbook

**Purpose:** One place to fix explorer public URL timeout and other documented issues.  
**References:** [EXPLORER_PUBLIC_URL_UNREACHABLE_FIX.md](EXPLORER_PUBLIC_URL_UNREACHABLE_FIX.md), [FIXES_PREPARED.md](../04-configuration/FIXES_PREPARED.md), [FULL_FIXES_PREPARED.md](../04-configuration/FULL_FIXES_PREPARED.md).

---

## 1. Explorer public URL timeout (ERR_CONNECTION_TIMED_OUT)

**Symptom:** Browser shows "explorer.d-bis.org took too long to respond" / ERR_CONNECTION_TIMED_OUT.

### 1a. This machine (ASERET / Linux WSL)

- **Already done:** `/etc/hosts` contains `192.168.11.140 explorer.d-bis.org` — curl and Linux tools use the backend directly.
- **If you removed it:**  
  `echo '192.168.11.140 explorer.d-bis.org' | sudo tee -a /etc/hosts`

### 1b. Windows (same PC — browser uses Windows hosts)

So that **Chrome/Edge on Windows** can reach the explorer:

1. Open Notepad **as Administrator**.
2. Open file: `C:\Windows\System32\drivers\etc\hosts`
3. Add a line: `192.168.11.140 explorer.d-bis.org`
4. Save. Flush DNS: open CMD as Admin → `ipconfig /flushdns`
5. Reload https://explorer.d-bis.org/ in the browser.

### 1c. Fix for all LAN clients (no hosts on each machine)

On **UDM Pro**: enable **NAT loopback** (hairpin) so traffic from LAN to 76.53.10.36 is forwarded to 192.168.11.167.

- UniFi Network → Settings → Firewall & Security (or Routing) → enable **NAT loopback** / **Hairpin NAT** if available.
- Then any device on the LAN can use https://explorer.d-bis.org without a hosts entry.

### 1d. External access (from internet)

Confirm **UDM Pro** port forward:

- **76.53.10.36:80** → **192.168.11.167:80** (TCP)
- **76.53.10.36:443** → **192.168.11.167:443** (TCP)

Test from a device **off the LAN** (e.g. phone on cellular): `https://explorer.d-bis.org/` → should return 200.

---

## 2. Other required fixes (from FIXES_PREPARED / FULL_FIXES_PREPARED)

| Item | Action | Doc |
|------|--------|-----|
| UDM Pro port forward (Alltra/HYBX) | Manual: 76.53.10.38 → 192.168.11.169 (80, 81, 443) | [FIXES_PREPARED.md §1](../04-configuration/FIXES_PREPARED.md#1-udm-pro-port-forward-alltrahybx) |
| Alltra/HYBX 502 | Verify backends (2500–2502, 2503–2505, 5201, 5202); fix NPMplus or deploy | [FIXES_PREPARED.md §2](../04-configuration/FIXES_PREPARED.md#2-alltrahybx-502-failures-required) |
| Validators / block production | Run validator fix; ensure 4/5 active | [FULL_FIXES_PREPARED.md §1](../04-configuration/FULL_FIXES_PREPARED.md) |
| Stuck tx / Sentry / RPC nodes | Per FULL_FIXES_PREPARED §§2–4 | [FULL_FIXES_PREPARED.md](../04-configuration/FULL_FIXES_PREPARED.md) |

---

## 3. Optional fixes (scripts from project root)

From repo root (`/home/intlc/projects/proxmox`):

```bash
# NPMplus certs (remaining Alltra/HYBX)
FIRST_ONLY=1 NPM_URL=https://192.168.11.167:81 bash scripts/request-npmplus-certificates.sh
NPM_URL=https://192.168.11.167:81 bash scripts/request-npmplus-certificates.sh

# Explorer SSL
# NPMplus UI → Proxy Hosts → explorer.d-bis.org → SSL tab → request/renew

# Env permissions
bash scripts/security/secure-env-permissions.sh

# Shellcheck (optional)
bash scripts/verify/run-shellcheck.sh --optional

# Full verification
bash scripts/verify/run-full-verification.sh
```

---

## 4. Quick checklist

- [ ] **Explorer from this machine:** hosts entry present → curl https://explorer.d-bis.org/ returns 200
- [ ] **Explorer from Windows browser:** Windows hosts has `192.168.11.140 explorer.d-bis.org` (or use UDM Pro hairpin)
- [ ] **Explorer from all LAN:** UDM Pro NAT loopback enabled (optional)
- [ ] **Explorer from internet:** UDM Pro 76.53.10.36:80/443 → 192.168.11.167
- [ ] **Other required:** Alltra/HYBX port forward and 502 fixes per FIXES_PREPARED / FULL_FIXES_PREPARED
- [ ] **Optional:** NPMplus certs, Explorer SSL, env permissions, shellcheck, full verification