> For the complete documentation index, see [llms.txt](https://docs.presearch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.presearch.io/nodes/setup/vps-setup/running-a-node-on-fluxos.md).

# Running a node on FluxOS

## Login on Flux

First, go to <https://home.runonflux.io/> and login with your ZelID. If you do not have a ZelID, then you must download Zelcore to the device of your choice here - <https://zelcore.io/>. Zelid is a btc address unique for for each zelcore account.

### Go to marketplace & select Presearch

{% embed url="<https://home.runonflux.io/apps/marketplace?q=presearch>" %}

### Enter registration code&#x20;

Enter your Presearch Registration Code from your[ Node Dashboard](https://nodes.presearch.org/dashboard).

![](/files/GR298mftJQccHZeoANXw)

### Configure the app&#x20;

Click Start Launching Marketplace App and then click Next.

### Sign the message&#x20;

Click the Sign App Message with Zelcore. Zelcore will open then click Approve to sign the message. Select Presearch Click on PresearchNode in the list of apps in marketplace. Go back to Flux and click the Next button to continue.

### Pay with Zelcore&#x20;

Click Pay with Zelcore, Zelcore will then open with all payment details populated. Click Send to send the payment.

### Launch your nodes!&#x20;

Once you've sent the payment, go back to Flux and click Finish. Once the next block has been mined your nodes will be spawned. In the left hand menu click Apps then Global Apps then My Apps and your nodes should be visible.

### Stake your PRE

Head to your [Node Dashboard](https://nodes.presearch.org/dashboad) to stake PRE on your nodes!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.presearch.io/nodes/setup/vps-setup/running-a-node-on-fluxos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
