Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- 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>

2026-02-12 15:46:57 -08:00

2.6 KiB

Raw Blame History

NPMplus Custom Config: wss://rpc.d-bis.org → 8546

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation

Purpose: Route WebSocket requests to rpc.d-bis.org to http://192.168.11.221:8546 while keeping HTTP RPC on 8545, so both wss://rpc.d-bis.org and wss://ws.rpc.d-bis.org work.

Option 1: Custom Nginx in proxy host (Advanced tab)

In NPMplus, open Hosts → edit rpc.d-bis.org.
Open the Advanced tab.
In Custom Nginx Configuration, paste the following at the top (so it runs before the default proxy_pass):

# Route WebSocket to 8546, HTTP stays on 8545
if ($http_upgrade ~* "websocket") {
    proxy_pass http://192.168.11.221:8546;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_cache_bypass $http_upgrade;
}

Save and let NPM reload Nginx.

Note: If your NPM version merges Custom config elsewhere (e.g. after proxy_pass), this may not take effect. In that case use Option 2 or rely on wss://ws.rpc.d-bis.org (no custom config).

Option 2: Custom file on NPM container

If the Advanced snippet is not applied before the default proxy_pass, add a custom include on the NPM host:

SSH to the Proxmox host, then into the NPM container (e.g. pct exec 10233 -- bash).
Create or edit /data/nginx/custom/rpc_d_bis_org.conf (path may vary; check NPM’s “Custom” include path).
Add a map at the top of the http block (or in the server block for rpc.d-bis.org if you have access), and ensure the proxy host’s location uses the variable. Many NPM setups do not allow this without editing the generated config; if so, use Option 1 or wss://ws.rpc.d-bis.org only.

Verification

HTTP RPC: curl -s -X POST https://rpc.d-bis.org -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' → "result":"0x8a".
WebSocket (rpc.d-bis.org): Use a client that connects to wss://rpc.d-bis.org and calls eth_chainId; expect 0x8a.
WebSocket (ws.rpc.d-bis.org): Same with wss://ws.rpc.d-bis.org (always works without custom config).

Summary

URL	Backend	Requires custom?
https://rpc.d-bis.org	192.168.11.221:8545	No
wss://rpc.d-bis.org	192.168.11.221:8546	Yes (snippet above)
wss://ws.rpc.d-bis.org	192.168.11.221:8546	No

2.6 KiB Raw Blame History Unescape Escape