> For the complete documentation index, see [llms.txt](https://docs.sia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sia.tech/legacy/your-sia-wallet/for-advanced-users/using-sia-on-a-remote-node.md).

# Using Sia on a remote node

## Using Sia on a remote node

While the majority of users use Sia on a local computer, there are a few instances where it is either not possible or more useful to run a Sia node on a remote server.

Sia already has the functionality to automatically pick up a running `siad` instance if one was started manually. To get Sia to pick up a remote instance, all you need to do is forward your local port 9980 to your remote server port 9980. For those comfortable with the command line, you can use the following command.

```
ssh -f user@domain -L 9980:localhost:9980 -N
```

`-f` Requests ssh to go to background just before command execution.

`-L` Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side.

`-N` Do not execute a remote command.

Now when you restart Sia, it will pick up the remote instance of siad. All API calls that don't require authentication will work, however API calls that require authentication will fail as the UI will be using the wrong API password. A workaround for this is to restart the remote siad instance with:

`--authenticate-api=false`

Now, all API calls will work and you can use Sia just like you would with a local siad instance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sia.tech/legacy/your-sia-wallet/for-advanced-users/using-sia-on-a-remote-node.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.