# Studio was unable to connect to "localhost" error with Unity 2021

**URL:** <https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271>\
**Category:** Unity\
**Created:** [September 13, 2022, 4:46am UTC](https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271 "2022-09-13T04:46:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [September 19, 2022, 4:47am UTC](https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271/2 "2022-09-19T04:47:38Z")

</div>

To start with it might be worth checking that nothing else is sitting on port 9264.  
Can you please try the following:

- Close Unity and FMOD Studio
- Open a windows command propmt
- Run the following command to enumerate processes listening on port 9264

```auto
netstat -a -n -o | find "9264"

```

- If that yields any results, for example:

```auto
C:\Users\User>netstat -a -n -o | find "9264"
TCP 0.0.0.0:9264 0.0.0.0:0 LISTENING 7688
TCP 127.0.0.1:9264 127.0.0.1:64289 ESTABLISHED 7688
TCP 127.0.0.1:64289 127.0.0.1:9264 ESTABLISHED 13804

```

then kill those processes:

```auto
taskkill /pid 7688 /f
taskkill /pid 13804 /f

```

After that, reopen Unity and FMOD Studio and see if you can connect to Live Update.

> [@simpsonelli](#):
>
> - I have updated the scripting define symbols in Unity to FMOD\_LIVEUPDATE

Please also rollback any changes you have made to the FMOD Unity integration, just to eliminate the possibility of any manual changes causing issues.

---

_[View the full topic](https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271)._