Troubleshooting Steps

Troubleshooting Steps

If you're experiencing issues with Quickscope's RPC or Router services, follow the checklist below to isolate and resolve the problem.

---

Request Header Validation

Ensure that your API request includes a valid key:

• Use the x-api-key header with your api-key
• Check that the key is active, not expired or malformed
• Keys must match the project associated with the endpoint

---

IP & Domain Whitelisting

If whitelisting is enabled:

• Confirm the request originates from an approved IP address or domain
• A 403 error typically means your request source isn't allowed
• Update your access settings in the Dashboard

---

RPC-Specific Checks

For RPC-related problems:

• Use the correct RPC endpoint: shared, private, or dedicated
• Refer to your assigned URL in the RPC Dashboard
• Performance issues may be tied to high request volume or endpoint mismatch

---

Router-Specific Checks

Router errors often relate to bad inputs:

• Validate token mint addresses, amounts, and fee settings
• Avoid extreme slippage or unsupported tokens
• Make sure you're using the correct URL format (e.g.,
  https://{region}.router.quickscope.so/api/v1/...)

---

Use the Built-In RPC Tester

You can diagnose issues via the RPC Testing panel:

• Send live requests and view raw output
• Test latency and payload size
• Access this via the RPC Dashboard – Testing Tab

---

Still Stuck?

Join our community for fast support and hands-on help:
discord.gg/quickscope

We're here to help troubleshoot edge cases or unusual errors.