> For the complete documentation index, see [llms.txt](https://docs.qms.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qms.finance/onboarding/troubleshooting-connections.md). # Troubleshooting Connections Most connection problems come down to three things: the wallet is on the wrong network, the RPC endpoint is unreachable, or the wallet is showing stale data. Work through the questions in order. **The application says I am on the wrong network, or that the chain ID does not match.**\ Open your wallet's network selector and choose **QMS Testnet**. If it is not listed, [add it](/onboarding/add-qms-network.md). If it is listed but the application still complains, open the network's settings in the wallet and check that the chain ID is 19480 and the RPC URL is exactly `https://rpc.testnet.qms.finance`. **My wallet cannot fetch the chain ID when I add the network.**\ The wallet could not reach the RPC endpoint. Check that the RPC URL has no typo, uses `https://`, and has nothing after the host name. Then check : if the RPC is reported down, wait and try again later. **My balance is still zero after using the faucet.**\ Paste your address into the search field at . If the explorer shows the transfer, your wallet has not refreshed: switch to another network and back, or close the wallet and open it again. If the explorer shows nothing, the faucet request did not go through. Request again; the faucet allows four requests in 24 hours. **The faucet refuses my request.**\ The faucet allows four requests in 24 hours and handles one request at a time. If you have reached the limit, wait for the window to pass; if it refused because another request was in progress, simply try again. **A transaction has been pending for a long time.**\ Look up the transaction hash on the explorer. If it is there and confirmed, the wallet is behind; reload it. If it is not there, the network is probably busy. When blocks are full, the base fee rises from block to block, and a transaction waits until the base fee is back below the maximum fee it allows. Some wallets set that maximum with little or no margin above the current base fee. The transaction goes through on its own once traffic drops. To get it in sooner, speed it up from the wallet's activity list. For your next transactions, raise the maximum fee in the wallet's advanced fee settings before you confirm. If it is still pending after traffic has dropped, see the question below about earlier transactions missing from the explorer. **A swap failed with an error saying the transaction expired.**\ Applications such as exchanges give each transaction a deadline. A transaction that waited past it, usually because the network was busy, is still included, but it fails and still costs a fee. Send it again with a higher maximum fee, set in the wallet's advanced fee settings before you confirm. If the application lets you set the deadline, lengthen it. **A transaction stays pending, and the explorer does not show my earlier transactions.**\ The test network has probably been reset, and the wallet is reusing an old nonce. In the MetaMask browser extension, for example, select QMS Testnet under **Network** on the Tokens tab, then open the menu and choose **Settings → Developer tools → Delete activity and nonce data**; the reset applies only to the account and network shown. In the MetaMask mobile app the option is **Settings → Advanced → Reset account**. Other wallets call it resetting the account or clearing pending transactions. Then send the transaction again. **A transaction failed with "transaction type not supported".**\ QMS does not accept type-3 (blob) transactions. This comes from a developer-side setting; see [EVM Compatibility](/for-developers/evm-compatibility.md). **None of this helps.**\ Ask on the [QMS Discord](https://discord.com/invite/qmsnetwork), with your address, the transaction hash if there is one, and the wallet you use.