> For the complete documentation index, see [llms.txt](https://help.defisaver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.defisaver.com/general/troubleshooting/my-metamask-account-is-failing-to-load-what-should-i-do.md).

# My MetaMask account is failing to load - what should I do?

When connecting to a dApp using MetaMask you are using the Ethereum node that is specified in your MetaMask configuration.

By default, MetaMask uses Infura as their node provider and does not have an alternative option as a fallback.

However, users can add other node providers in MetaMask and switch to those when needed.

{% hint style="info" %}
*Connecting with any other wallet type (e.g. connecting a Ledger or Trezor hardware wallet directly or connecting via WalletConnect) would be using the nodes used by DeFi Saver.* \
\
*If you're experiencing issues with connecting using MetaMask and have access to any of these other wallets, we suggest trying any of those first.*
{% endhint %}

## How to add and use a different node provider in MetaMask

The process is relatively simple, although the option is somewhat burried in the menus.

These are the steps:

<figure><img src="/files/Wu9Nxj9aTh2GRljwD7xs" alt=""><figcaption></figcaption></figure>

Once you're on the "Add Network" screen you should enter the details of an alternative node provider you selected.

For a list of numerous options, along with their current service status, please see [Ethereum Nodes](https://ethereumnodes.com/).

Once you've chosen your provider and entered their RPC URL, you can set any Network Name (e.g. Alchemy Ethereum) and you will need to set the Chain ID to "1". Other fields are needed.


---

# 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://help.defisaver.com/general/troubleshooting/my-metamask-account-is-failing-to-load-what-should-i-do.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.