> For the complete documentation index, see [llms.txt](https://docs.strnan.top/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strnan.top/testnet/nulink/troubleshooting.md).

# Troubleshooting

If you have some problem with your node and still offline on staking dashboard, you can do this way to make your node online.

### Open Port

{% hint style="danger" %}
Remember to use this command one by one to avoid some of this command not applied.
{% endhint %}

```
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh
sudo ufw allow 22
sudo ufw allow 9151/tcp
sudo ufw enable
```

Now you can check if your port is open or not with this [link](https://www.yougetsignal.com/tools/open-ports/).

Put **Remote Address** with your **VPS IP** and **Port Number** 9151 to make sure if your node port is open.

### Send tBNB to Worker Account

Most likely you didn't read all the guide i provided and you didn't send the tBNB to your worker. If you confuse which one is worker account, you can find it when you generate [geth account](/testnet/nulink/installation.md#generate-ethereum-account-and-keystore) and then send some tBNB like 0.05 or 0.1 or it's up to you.


---

# 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.strnan.top/testnet/nulink/troubleshooting.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.