# Holesky RPC Transaction Failure Metamask UI Bug

**URL:** <https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073>\
**Category:** Sending and Receiving Tokens\
**Created:** [January 27, 2024, 2:50am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073 "2024-01-27T02:50:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![entropy](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/entropy/32/33749_2.png) [@entropy](https://community.metamask.com/u/entropy)\
**Post date:** [January 27, 2024, 2:50am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073/1 "2024-01-27T02:50:17Z")

</div>

I added Holesky Testnet to MetaMask by using RPC ethpandaops and this resulted in a failure with a “internal JSON error”. I saw on Etherscan that the transaction still went through. However, on MetaMask UI the transaction still shows Failed. Any way to change that status to otherwise? It’s irritating seeing a Red Failure when in fact it went through.

 ![Screenshot 2024-01-27 at 10.49.26 AM](https://europe1.discourse-cdn.com/metamask/original/3X/f/b/fba87386b08dfedea5ce38dabb920fcfb808fe65.png)

---

<div class="post-metadata">

**Author:** ![tuya](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/tuya/32/15138_2.png) [@tuya](https://community.metamask.com/u/tuya)\
**Post date:** [January 27, 2024, 3:03am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073/2 "2024-01-27T03:03:19Z")

</div>

hey @entropy ,welcome to MetaMask community.  
I encountered a similar situation and it was a UI bug of MetaMask. As users, there may not be much we can do.  
Once you understand the bug, check its transaction status on explorer every time.

---

<div class="post-metadata">

**Author:** ![entropy](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/entropy/32/33749_2.png) [@entropy](https://community.metamask.com/u/entropy)\
**Post date:** [January 27, 2024, 5:25am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073/3 "2024-01-27T05:25:20Z")

</div>

Thanks! Glad to know it’s just a UI bug. That transaction was done using ethpanda RPC… I switched to publicnode later and it was successful. I wonder if this was a RPC issue as well?

---

<div class="post-metadata">

**Author:** ![tuya](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/tuya/32/15138_2.png) [@tuya](https://community.metamask.com/u/tuya)\
**Post date:** [January 27, 2024, 8:07am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073/4 "2024-01-27T08:07:25Z")

</div>

I think so. When we encounter similar errors, switching RPC may solve the problem. 😄

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/metamask/original/3X/3/8/3812168020a49f264784b1dbfcf12435abbb09ad.png) [@system](https://community.metamask.com/u/system)\
**Post date:** [February 26, 2024, 2:51am UTC](https://community.metamask.com/t/holesky-rpc-transaction-failure-metamask-ui-bug/28073/5 "2024-02-26T02:51:00Z")

</div>

Closed on February 26, 2024, 2:51am UTC

This topic was automatically closed after 30 days. New replies are no longer allowed.