---
description: This page attempts to provide solutions for common issues.
---

# Troubleshooting

#### Default RPC URL Issues

When making function calls to different chains, **block3d** will use the [default RPC URLs](https://github.com/wevm/viem/blob/main/src/chains/index.ts) provided by [wagmi](https://wagmi.sh/) if one isn't provided in the [config](getting-started/config). However, this causes issues because the default RPC URLs aren't always working properly. To fix this, explicitly add an RPC URL into your [wagmi](https://wagmi.sh/) config for the chain that isn't working properly.

#### Rules are not being recognized

If a rule in the `block3dConfig` isn't being recognized, this is likely due to a syntax error. Only rules that have correct syntax will be acknowledged by block3d. Please see the [`Rule`](types) type as well as the [Config](getting-started/config) page for more information.

#### Error: Functions cannot be passed directly to Client Components

If you are seeing this error from Next js, the reason is probably because the root `layout.tsx` or `app.tsx` file isn't marked as `"use client";`. Currently, **block3d** only works correctly with [Client Side Rendering](https://nextjs.org/docs/app/building-your-application/rendering/client-components#using-client-components-in-nextjs).

#### Additional issues

If you run into problems that aren't described on this page, please open an issue [here](https://github.com/RohanNero/block3d/issues).
