koobas.hobune.stream
I keep getting an error regarding the Unity Package Manager, and no solution I have seen on here is working...
I just updated to Unity 2017.2, and every time I try to open a new or existing file, I get this error message after watching a progress bar of 25% sit frozen for ten seconds: Failed to start Unity Package Manager: operation timed out. Please see the Editor.log file for more information. I have deleted and reinstalled, I have gone to the terminal and returned the localhost, I cannot seem to find any kind of solution. Has anyone run into this on a Mac?
Here is the info I get in my editor.log
[Package $$anonymous$$anager] Server::Start -- Port 50123 was selected Launching external process: /Applications/Unity/Unity.app/Contents/Tools/nodejs/bin/node /Users/Batcomputer/New Unity Project 1 Audio: F$$anonymous$$OD Profiler initialized on port 54900 Loading GUID <-> Path mappings...0.000083 seconds Loading Asset Database...0.000008 seconds AssetDatabase consistency checks...0.000185 seconds Refreshing native plugins compatible for Editor in 0.01 ms, found 0 plugins. Preloading 0 native plugins for Editor in 0.00 ms. [Package $$anonymous$$anager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds [Package $$anonymous$$anager] Server::$$anonymous$$ill -- Server was shutdown [Package $$anonymous$$anager] Package$$anonymous$$anager Server::Start -- Process restart attempt #8
It keeps making attempts, but I have no clue what the issue is. I'm new...
I'm getting the same thing on PC. I submitted a bug report and linked to this question.
I can't post my answer because of some issue with the captcha. Here it is as a comment.
Hi,
We have found one 100% repro step for this issue. An empty host file was 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
$$anonymous$$ake sure the localhost host name is defined like this
127.0.0.1 localhost
Let me know if it resolve the issue!
Pascal
This worked! Thank you so much. Right after the local host was this tag #Activation blocker. So I removed that and saved and Unity booted right up. Can't wait to start developing with this amazing tool. Thank you again!
Jimmy
Hi!
If there is still someone with the same error, try this:
On Windows > command prompt,
setx UNITY_NOPROXY localhost
On Mac > terminal,
export UNITY_NOPROXY=localhost
This will fix the error.
It is worth remembering that Unity has already corrected this error in later versions.
Cheers!
Hi @datCloud,
Thanks a lot for sharing this. I’ll add this recommendation in my response.
Regards,
Pascal
Update: The issue should be fixed in Unity 20172.0p4.
If not, please send us a bug report.
Pascal
--------------------------------------------------------------------------------------------------------
Hi,
We have found one 100% repro step for this issue. 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
Another solution other users have reported to work is to set the
UNITY_NOPROXY environment variable to
localhost:
On Windows command prompt,
setx UNITY_NOPROXY localhost,127.0.0.1
On Mac > terminal,
export UNITY_NOPROXY=localhost,127.0.0.1
If this fix does not work or if your hosts file is already correct, we also found out that anti-virus softwares can prevent the Unity Package Manager process to start. In that scenario, you can disable your anti-virus software for a few minutes to test if it works. If it did, configure your anti-virus to whitelist the NodeJS bundled with Unity (Under Unity installation folder, /Tools/nodejs/node.exe on Windows of /Tools/nodejs/bin/node on other platforms).
Let me know if it resolve the issue!
Pascal
This work, but in part, because after I updated to High Sierra the message does not appear more, but my system was cracked and I need to power off my machine. So my solution was to install the patches manually one by one the Editor(...).pkg, the standardassets.pkg and the examples.pkg, so if any have the same problem I believe my machine is exactlly like other $$anonymous$$ac with the Sierra OS. Now after patched, the editor is working fine here, but I dont know what I need to do with the "builtin_shaders-2017" and "CacheServer" folders. Someone can tell-me what I need to do with these folders? thanks
Experienced this issue (or a similar one) with both 2017.3.0f3 and 2017.3.0p4 when opening a project from an existing Unity session. The host file solution alone didn't fix the issue for me, but after setting UNITY_NOPROXY everything seems to be working again.
same to me. hmm... -_-;
Had to revert to 2017.1. No response from Unity yet. If I don't hear back soon I'll reach out to support.
Same here. Until this update, everything worked fine.
Environment: macOS Sierra 10.12.6
Hi, I'm a mac user, and struggling with this for a week, had to revert to 2017.1 as well.
