# Umbrel’s Bitcoin Core Remote Procedure Calls (RPC) with Local Port Forwarding

**URL:** <https://community.umbrel.com/t/umbrel-s-bitcoin-core-remote-procedure-calls-rpc-with-local-port-forwarding/21978>\
**Category:** Support and Troubleshooting\
**Created:** [March 23, 2025, 9:12pm UTC](https://community.umbrel.com/t/umbrel-s-bitcoin-core-remote-procedure-calls-rpc-with-local-port-forwarding/21978 "2025-03-23T21:12:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbasile](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/mbasile/32/6702_2.png) [@mbasile](https://community.umbrel.com/u/mbasile)\
**Post date:** [March 23, 2025, 9:12pm UTC](https://community.umbrel.com/t/umbrel-s-bitcoin-core-remote-procedure-calls-rpc-with-local-port-forwarding/21978/1 "2025-03-23T21:12:51Z")

</div>

As you probably have discovered, the Bitcoin Core on Umbrel does not expose Remote Procedure Calls (RPC), hence it does not accept RPC from an External Host.

In other words, any API call from an external host (e.g. your laptop) to the Bitcoin Core running on the Umbrel server will fail.

One simple workaround is using ssh tunneling.  
You find a step by step guide at the following Google Doc:  
[Umbrel’s Bitcoin Core Remote Procedure Calls (RPC) with Local Port Forwarding](https://docs.google.com/document/d/1KbsKXFN3Niel_IyqG9dmQncu5NRO1-mkvYHRGd8OG9Q/edit?usp=sharing)