# Issue with Live Connecting in 2.02.15

**URL:** <https://qa.fmod.com/t/issue-with-live-connecting-in-2-02-15/20505>\
**Category:** FMOD Studio\
**Created:** [August 7, 2023, 12:09am UTC](https://qa.fmod.com/t/issue-with-live-connecting-in-2-02-15/20505 "2023-08-07T00:09:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [August 7, 2023, 1:22am UTC](https://qa.fmod.com/t/issue-with-live-connecting-in-2-02-15/20505/2 "2023-08-07T01:22:19Z")

</div>

Hi,

This issue is typically caused by port 9264 being used by another instance of FMOD Studio, or another process. The following post contains instructions on how to identify whether another process is using the port: [Studio was unable to connect to "localhost" error with Unity 2021 - #2 by jeff\_fmod](https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271/2)

> [@Studio was unable to connect to "localhost" error with Unity 2021](https://qa.fmod.com/t/studio-was-unable-to-connect-to-localhost-error-with-unity-2021/19271/2):
>
> 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
> 
> ```

Please give this a shot and see whether it resolves the issue.

---

_[View the full topic](https://qa.fmod.com/t/issue-with-live-connecting-in-2-02-15/20505)._