# Sandbox UI - Error 500 on EOS\_TEST asset wallet creation

**URL:** <https://community.fireblocks.com/t/sandbox-ui-error-500-on-eos-test-asset-wallet-creation/1280>\
**Category:** Support\
**Created:** [August 6, 2024, 11:29am UTC](https://community.fireblocks.com/t/sandbox-ui-error-500-on-eos-test-asset-wallet-creation/1280 "2024-08-06T11:29:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JLL](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JLL](https://community.fireblocks.com/u/JLL)\
**Post date:** [August 6, 2024, 11:29am UTC](https://community.fireblocks.com/t/sandbox-ui-error-500-on-eos-test-asset-wallet-creation/1280/1 "2024-08-06T11:29:35Z")

</div>

Hello there,  
I am getting the following error :

```auto
NetworkServiceError: Failed fetching "https://sb-console-api.fireblocks.io/generate_eos_account?asset=EOS_TEST", status:500
    at GXt.fetch (NetworkService.ts:143:13)
    at async GXt.get (NetworkService.ts:114:20)
    at async Zye.generateEOSAccount (Api.ts:1065:22)

```

As soon as I try to create a EOS\_TEST asset wallet  
Steps:

1. [Fireblocks Console](https://sandbox.fireblocks.io/v2/accounts/vault/0) (sandbox)
2. Create wallet
3. Create asset wallet
4. EOS\_TEST

Notes  
No error message is displayed directly in the page, field is set to disabled , everything is stuck, you have got to inspect to see the issues and relevant error messages

Env  
Mac Os + Ventura + Chrome 127.0.6533.89 (Official Build) (arm64)

Thank you in advance for your help

---

<div class="post-metadata">

**Author:** ![Wilfred](https://sea1.discourse-cdn.com/flex015/user_avatar/community.fireblocks.com/wilfred/32/403_2.png) [@Wilfred](https://community.fireblocks.com/u/Wilfred)\
**Post date:** [August 7, 2024, 7:54am UTC](https://community.fireblocks.com/t/sandbox-ui-error-500-on-eos-test-asset-wallet-creation/1280/2 "2024-08-07T07:54:20Z")

</div>

Hi @JLL thank you for raising this to our attention. I was able to reproduce this error and will escalate this internally.

It looks like currently, the EOS\_TEST integration is not active resulting in these 500 errors.

We will update you once R&D have implemented a fix.