fbda1b4beb
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
3.7 KiB
✅ Direct Blockscout Route - All Changes Applied
Date: 2026-01-18
Status: ✅ All Configuration Files Updated
🎯 Objective
Configure a direct route to Blockscout, bypassing nginx on VMID 5000 to fix 502 Bad Gateway errors.
Route Change:
- ❌ Old:
NPMplus → 192.168.11.140:80 (nginx) → 127.0.0.1:4000 (Blockscout) - ✅ New:
NPMplus → 192.168.11.140:4000 (Blockscout directly)
✅ Files Updated
Active Configuration Scripts (Updated)
-
✅
scripts/nginx-proxy-manager/configure-npmplus-domains.js- Changed:
explorer.d-bis.org→http://192.168.11.140:4000
- Changed:
-
✅
scripts/nginx-proxy-manager/configure-ssl-all-domains.js- Changed:
explorer.d-bis.org→http://192.168.11.140:4000
- Changed:
-
✅
scripts/nginx-proxy-manager/configure-ssl-api.js- Changed:
explorer.d-bis.org→http://192.168.11.140:4000
- Changed:
Documentation (Updated)
-
✅
docs/04-configuration/RPC_ENDPOINTS_MASTER.md- Updated port: 80 → 4000
- Added note: "Direct Route - bypasses nginx"
-
✅
docs/04-configuration/ALL_VMIDS_ENDPOINTS.md- Updated port: 80 → 4000
- Added note: "Direct Route"
-
✅
docs/04-configuration/DIRECT_BLOCKSCOUT_ROUTE_UPDATE.md(NEW)- Complete documentation of the change
- Instructions for applying updates
New Scripts Created
-
✅
scripts/configure-direct-blockscout-route.sh- Diagnostic script to check Blockscout configuration
- Verifies network accessibility
-
✅
scripts/apply-direct-blockscout-route.sh- Main script to apply the direct route configuration
- Automates NPMplus update
-
✅
scripts/nginx-proxy-manager/update-explorer-direct-route.js- Automated NPMplus configuration update
- Uses Playwright browser automation
-
✅
scripts/diagnose-explorer-502-error.sh- Comprehensive diagnostic tool for 502 errors
⏳ Action Required
Apply NPMplus Configuration
The configuration files are updated, but NPMplus needs to be updated to use the new route.
Option 1: Automated (Recommended)
From a machine that can access NPMplus:
cd /home/intlc/projects/proxmox
./scripts/apply-direct-blockscout-route.sh
Option 2: Manual Update
- Log into NPMplus:
https://192.168.0.166:81 - Navigate to Proxy Hosts
- Find
explorer.d-bis.org - Update:
- Forward Host:
192.168.11.140 - Forward Port:
4000(change from 80)
- Forward Host:
- Save changes
🔍 Verification Steps
After applying NPMplus update:
-
Test API:
curl -I https://explorer.d-bis.org/api/v2/statsShould return HTTP 200 (not 502).
-
Check Browser Console:
- Open
https://explorer.d-bis.org - Check console for errors
- Verify API calls succeed
- Open
-
Verify Direct Connection:
curl -I http://192.168.11.140:4000/api/v2/statsShould work if Blockscout is network accessible.
📋 Prerequisites Check
Before the direct route will work, ensure:
- Blockscout service is running
- Blockscout is listening on port 4000
- Blockscout is network accessible (0.0.0.0:4000, not just 127.0.0.1:4000)
Run diagnostic:
./scripts/configure-direct-blockscout-route.sh
📚 Related Files
- Main Documentation:
docs/04-configuration/DIRECT_BLOCKSCOUT_ROUTE_UPDATE.md - Master Reference:
docs/04-configuration/RPC_ENDPOINTS_MASTER.md - All Endpoints:
docs/04-configuration/ALL_VMIDS_ENDPOINTS.md
🎉 Summary
✅ All configuration files updated
✅ All documentation updated
✅ Diagnostic and update scripts created
⏳ NPMplus configuration update pending (run ./scripts/apply-direct-blockscout-route.sh)
Next Step: Apply the NPMplus configuration update to complete the direct route setup.