Unity 2018.3.0f2 Package Manager Error after selecting project

Question

I used Unity 5.4.2 several years ago. I tried to upgrade to 2017 and 2018, but whenever I try to start a Project, or open an existing project, the unitypackagemanager.exe fails to connect to local server. I tried at add an environmental variable for Unity_NoProxy, running as administrator, setting all the executables to run as admin, disabled the firewall, made an outgoing rule for the firewall, set inbound permissions to allow for public and private. I don't know what else I can specifically do to made sure the process can access the HTML on 127.0.0.1. Any ideas will be greatly appreciated. alt text link text

Answer 1

Best Answer

Answer by rwlangbe · Jan 12, 2019 at 04:57 AM

I got Unity 2018.3.1f1 to RUN, finally.
The Unity Package Manager function was crashing the Program for some unknown reason. My short term fix is to turn off the function by adding -noUpm as a parameter after the executable. I highly suggest, if you're having this problem, to create a shortcut and add -noUpm in the target line of the shortcut after Unity.exe.

I have no idea how this is going to affect me later. If Anyone has an idea, please let me know. Also, how many people have to modify the shortcut or add parameters just to run the damn program? It seems a bit ridiculous.

Add comment · Show 2 · Share

rwlangbe · Jan 11, 2019 at 04:41 AM 0

Share

I still haven't found the answer to this, but I have noticed when I start Unity the Node.exe process (Server?) has already stopped. It seems that when I select a Project, Unity has already crashed behind the scenes, so this error message is secondary and has nothing to do with Localhost.

I don't know why Node.exe is stopping, but the entire contents of the editor.log file (renamed to .txt for I can include it here) were created before I even select a project.

rwlangbe · Jan 12, 2019 at 03:54 PM 0

Share

Another Fun Fact - If you try to run Unity.exe andyou get the screen that says, redo the license, you can run Unity.exe without -noUP$$anonymous$$. Just run the executable normally, and the Package manager will Work! Brilliant job there Unity....Great job!

Unity 2018.3.0f2 Package Manager Error after selecting project

I re-installed Unity 2018.3.1f2 complete package today to see if this is working, and the same exact failure happened.

1 Reply

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions