Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.3.1p1
Issue ID
1013731
Regression
No
[Windows 7] Local cache server can't connect
Reproduction steps:
1. Create a New Project
2. Enable the Local Cache Server
3. Exit the Editor
4. Open the same project
5. Look at the Console window
Expected Result: No errors appear in the Console
Actual Result: "Socket: connect failed, error: No connection could be made because the target machine actively refused it."
Reproduced with: 2018.2.0a7, 2018.1.0b13, 2017.4.1f1, 2017.3.2f1, 2017.2.2p3, 2017.1.3p3
-
GameRocker
Jun 12, 2019 15:58
I have this error on Unity 2019.1.5f and windows 10.
-
Trisibo
Nov 24, 2018 23:26
I've had this problem since I can remember, now with 2018.2.16f1, Windows 10 Pro.
-
Xtro
Aug 05, 2018 16:23
Seems to be fixed on 2018.2.2
-
dserebroDXC
May 23, 2018 02:42
Having same issue on 2018.1.0f2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] HDAdditionalLightData.RequestSubShadowMapRendering on directional lights breaks cascade shadows rendering
- Memory leaks when Instantiating Objects with SerializeReference
- Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
- "F" default focusing Unity shortcut zooms out when the first time focusing the GameObject
- DropdownField options added with PointerDownEvent are not shown when clicking the DropddownField for the first time
Resolution Note:
This can be worked around by setting up the GitHub hosted Cache Server independently from Unity, and connecting to it like a "remote" cache server with "localhost[:port]" (port is 8126 by default) as the host name. https://github.com/Unity-Technologies/unity-cache-server