> For a complete page index, fetch https://docs.conduit.xyz/llms.txt

# Run an Arbitrum Orbit Node

> Complete guide to setting up and running an Arbitrum Orbit node on Conduit. Learn how to configure settings, gather required information, and set up external nodes for self-hosting.

> **Info**
>
> At this time, the setup and maintenance of self-hosted nodes are not included in Conduit’s standard scope of support. The guide below provides a high-level overview for setting up an external node. Please note that, due to frequent updates to the underlying software, additional configuration steps or variables may be required.
>
> If you’re onboarding a partner or tool, we recommend using [Conduit Nodes](https://conduit.xyz/nodes) — the managed, production-ready version of nodes for your RPC needs. Conduit RPC nodes are actively maintained, monitored, and optimized to scale with your network’s performance requirements.
>
> If you’d like to maintain a backup RPC provider, we suggest [Tenderly](https://tenderly.co/), an approved Conduit vendor.

To run a self-hosted node for an Arbitrum rollup deployed on Conduit, please follow the steps below to configure the necessary settings and gather all required information. Afterwards, you can proceed with [Conduit's Github Repository](https://github.com/conduitxyz/conduit-arbitrum-external-node) on how to run a node.

#### Sign in

Log in to the [Conduit app](https://app.conduit.xyz).

#### Access settings

Navigate to your deployment dashboard. Click on `Settings`, then select `General` from the sidebar.

#### Enable external nodes

Activate the `Enable external nodes` setting. **Note**: If you wish to disable this setting later, please contact our [Support](https://portal.usepylon.com/conduit-xyz/forms/support-request).

#### Gather required information from the deployment dashboard

Navigate to the Deployment Dashboard. Go to the `Overview` section and click the `Run a Node` button on the right side.

OR

Visit the [Conduit Hub](https://hub.conduit.xyz/) if the network is public, select the network and click on `Run a Node`.

#### Access configuration files

You will find the `Websocket URL` for the `Sequencer Feed Relay` and `HTTP URL` for the `AnyTrust DA (Fallback)` and other required parameters in the same popup.

#### Next steps

You should now have all the information about your Rollup that is needed to run your own self-hosted node. Follow [Conduit's Repository](https://github.com/conduitxyz/conduit-arbitrum-external-node) for the next Steps.

### Snapshots

You can initialize Arbitrum external nodes from Conduit snapshots. Snapshots can take up to 4 hours to become available after you enable external nodes. Conduit stores the snapshots in a requester-pays Google Cloud Storage bucket, so you need a Google Cloud project with billing enabled. You also need the `roles/serviceusage.serviceUsageConsumer` role on the billing project. See the [requester-pays requirements](https://docs.cloud.google.com/storage/docs/requester-pays#requirements).

Conduit refreshes snapshots on the first and fifteenth of each month. The job starts at 16:00 UTC and most networks finish within about 4 hours.

Set `NETWORK` to your network slug from the Conduit dashboard or Hub. Set `CLOUDSDK_BILLING_QUOTA_PROJECT` to the Google Cloud project that pays for the download. Set `DATADIR` to the directory where you want to extract the snapshot.

```bash
(
  set -euo pipefail
  export LC_ALL=C
  export CLOUDSDK_BILLING_QUOTA_PROJECT="<billing-project-id>"

  NETWORK="<network>"
  DATADIR="<path/to/datadir>"
  PREFIX="gs://conduit-networks-snapshots/${NETWORK}"

  mkdir -p "${DATADIR}"
  WORK="$(mktemp -d "${DATADIR}/.snapshot.XXXXXX")"
  trap 'rm -rf "${WORK}"' EXIT

  if gcloud storage ls "${PREFIX}/snapshot_part_aa.tar.part" >/dev/null 2>&1; then
    gcloud storage cp "${PREFIX}/snapshot_part_*.tar.part" "${WORK}/"
  else
    gcloud storage cp "${PREFIX}/latest.tar" "${WORK}/"
  fi

  cat "${WORK}"/* | tar -xf - -C "${DATADIR}"
)
```

Conduit splits snapshots larger than 5 TB into files such as `snapshot_part_aa.tar.part` and `snapshot_part_ab.tar.part`. The command downloads multipart snapshots in parallel and streams the parts into `tar` in filename order. It doesn't create a second assembled archive. If no multipart snapshot exists, the command downloads and extracts `latest.tar` instead. After extraction, it removes the downloaded archive files.

> Complete guide to setting up and running an Arbitrum Orbit node on Conduit. Learn how to configure settings, gather required information, and set up external nodes for self-hosting.