Diagnose a Geth method that works over IPC but fails over HTTP
A successful local console call does not establish that the same RPC namespace is exposed on the public-facing transport. Compare capabilities at each hop.
Probe the actual transport
Submit the request below over HTTP, then issue the same method over an authorized local IPC connection. If rpc_modules is available, compare the namespace names returned by each connection.
{"jsonrpc":"2.0","id":1,"method":"rpc_modules","params":[]}
An eth entry together with an absent debug entry can explain why a basic block lookup succeeds while a trace gets method not found. Also run the target read-only method itself: a gateway can filter individual methods after the Geth transport accepts them.
Find which layer owns the difference
Compare direct backend HTTP with the gateway route and inspect Geth’s transport-specific API configuration. Keep privileged debugging methods on a restricted path if only operators use them. A transport inventory is a point-in-time observation of this endpoint. geth.ethereum.org Geth JSON-RPC server