It will stuck in “Starting Server…” for a while, and then notice that “Failed to start Unity Package Manager: operation timed out. Please see the Editor.log file for more information.” No matter if the old projects or a new one.
Were you able to solve this? I have the exact same problem…
Have you checked the Editor.log for more information?
These are the last few rows in the Editor.log. If I re-install Unity it will work for a while, and then this problem appears again.
[Package Manager] Server::Start – Port 62563 was selected
Launching external process: /Applications/Unity/Unity.app/Contents/Tools/nodejs/bin/node
[Package Manager] Failed to start Unity Package Manager: operation timed out.
[Unity Package Manager (Upm)] - Application terminated due to HTTP connection being closed on the other end.
@JeffDUnity3D any ideas I can try?
Are you going through a proxy or firewall? Unity 2017.2 not working,Unity package manager error. - Questions & Answers - Unity Discussions . If on Windows, can you run as Administrator?
@JeffDUnity3D No, neither - and I am on Windows. The same problem occurs when I am offline. It seems to be something with the NodeJS server?
Hm. I tried to switch to another Internet Connection and there it works.
Hi everyone, I’m sorry to reply this issue so late. Unity QA team has emailed me that changing the hosts file could fix this, and indeed, it works. Below are the details:
An empty hosts file is the cause. We have a fix in the way. But in the meantime, can you check the content of your hosts file. It should be located here:
On Windows:
C:\Windows\System32\drivers\etc\hosts
On macOS:
/etc/hosts
Make sure the localhost host name is defined like this
127.0.0.1 localhost