> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/legacy/troubleshooting-guide.md).

# Panduan Pemecahan Masalah

Di sini Anda akan menemukan bantuan langkah-demi-langkah untuk:

* Menyetor SOL → RSOL (pengaturan dompet, faucet, kesalahan transaksi)
* Menarik RSOL → SOL (alur penukaran, visibilitas token)
* Rome EVM (koneksi dompet, interaksi kontrak)
* Rome L2 Stack (instalasi, penggunaan, kesalahan umum)
* Rome SDK (instalasi, penggunaan, kesalahan umum)

Anda sedang menguji di Testnet, bagian ini dirancang untuk segera menyelesaikan masalah dan mengembalikan Anda ke pembangunan di Rome.

{% hint style="info" %}
Catatan

> Bagian pemecahan masalah ini masih dalam pengembangan. Saat ini, bagian ini hanya mencakup masalah yang paling umum. Kami akan terus memperluas panduan ini dan memperbarui dokumentasi dengan kasus pemecahan masalah tambahan berdasarkan masukan pengguna dan penggunaan di dunia nyata.
> {% endhint %}

\ <br>

\ <br>


---

# 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.rome.builders/id/legacy/troubleshooting-guide.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.
