1st: Install 2018.2.0b1
2nd: Create New Project
3rd: I got this screenshot.
I re-tried to open the project about five times.
I got this dialog message few minuet later.
Continue it, Unity was opened but I got the message.
This is same as 2018.1.0b13…
1 Like
Hi Iriguchi,
Could you please file a bug report for this issue and reply in here with the case #?
Hi @iriguchi ,
Sorry to see you are still affected by this issue. I saw from your other post ( Unity Package Manager Error ) that 2017.3.f1 works for you but not 2018.1. And now 2018.2 too!
This is really strange. Can I ask you to try with a later version of 2017.3 to see if the bug start showing up? (Download Archive)
Seems that all the latest versions fails for you.
The only hypothesis I could get out of this at this point is an anti-virus issue. But you are saying you have turned off the anti-virus and you still get the error right?
Regards,
Pascal
Hi Pascal,
I tested 2017.3.1p4 but Package Manager was crashed… case 1028247
I think this crash is same as 2017.4.0f1 and 2017.4.1f1.
An workaround “Run as administrator” has not effect.
And I tried to turn off the ESET but I got same crash dialog.
I tested another version of path release.
2017.3.1p1 is OK!!
2017.3.1p2 is OK!!
2017.3.1p3 is NG!!
Thanks,
Hirokazu
1 Like
Ok. So the bug has started to appear for you when we fixed all the issues for the others. This is strange. You are in a bizarro world 
The only thing left I can think of at the moment is that you may have overridden the UNITY_NOPROXY environment variable? Is the env var defined on your system? If so, what is the value? Can you try deleting the env var?
Pascal
Hi Pascal,
There is no UNITY_NOPROXY environment.
There are http_proxy and https_proxy environments for our proxy.
BTY,
I found that they have same problem.
Ok. This removes the proxy issue option. Thanks.
You stated that you have the problem with 2018.2.0b1. I believe we have a new log file in this version. Do you have a file named upm.log in the editor logs folder (Unity - Manual: Log files) ?
If yes, can you share the content after there was a failure to start Unity 2018.2.0b1?
Thank you!
Pascal
1 Like
Hi Hirokazu,
Thank you for the log files. I believe I now have a better idea what could be causing issues on your end.
This line from the upm.log file is the key point:
{"message":"Error while fetching config from https://public-cdn.cloud.unity3d.com/config/production: tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\\ssl\\s23_clnt.c:797:\n","stack":"Error: Error while fetching config from https://public-cdn.cloud.unity3d.com/config/production: tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\\ssl\\s23_clnt.c:797:\n\n at downloadConfigFile (C:\\snapshot\\upm\\packages\\services-config\\index.js:0:0)\n at <anonymous>","level":"error","timestamp":"2018-04-24T01:15:21.713Z"}
This is a proxy issue. Package Manager cannot reach the configuration service because you are behind a proxy.
Can you try setting proxy env vars?
export HTTP_PROXY=“http://user:password@host:portnumber”
export HTTPS_PROXY=“http://user:password@host:portnumber”
Replace user, password, host and portnumber with the ones of your proxy.
I’ll update the ticket with this new information. This will be really helpful to fix the problem.
Regards,
Pascal
1 Like
Hello @iriguchi ,
I’m very sorry you’re running into all these issues while attempting to start Unity. We have attempted to reproduce the issue using the versions that have failed and were unfortunately unsuccessful. If I could ask more details from you, this could inch us closer to a potential cause and resolution.
-
Would you try starting Unity without a network connection and let me know if you are able to start Unity with your project?
-
If the step above fails, could you try to start a new project with the same conditions mentioned above and let me know if that works?
-
Would you please paste the following URL on your browser “https://public-cdn.cloud.unity3d.com/config/production” and let me know what the response is?
-
It should look like this: Imgur: The magic of the Internet
Ultimately, please confirm the following for me:
- Node is not blocked at the firewall level
- No antivirus is running on your machine. If there is one active, it doesn’t block Unity processes.
- Under the location where your executable lies Path to your executable (in my case == C:\Program Files\Unity 2017.3.0a1) \Editor\Data\Resources\PackageManager\Editor please confirm that there are .tgz files in there like this: Imgur: The magic of the Internet
Thank you so much for your help and please accept my sincere apologies for the issues you’re running into.
Pedro
Unity STE
Hi Pascal and Pedro,
I fixed this problem with your advice.
Thank you for your support.
I found the mistake HTTPS_PROXY environment setting.
Like this.
export HTTP_PROXY=“http://host:portnumber”
export HTTPS_PROXY=“https://host:portnumber”
I typo “https”.
I fixed it to “http”, The Package Manager works fine.
.
I guess the package manager change the environment to use form HTTP_PROXY to HTTPS_PROXY
at the version 2017.3.1p3.
Thanks again.
Hirokazu
Thank you @iriguchi ,
We didn’t notice the typo on our end either. I’m so glad the situation has resolved itself. I will investigate what happened on version 2017.3.1p3.
And finally, Hirozaku, thank you for your patience as you worked with us in getting the problem addressed. It is thoroughly appreciated!
Pedro
STE
@pedro_unity
I had the same problem with 2018.1 and one of your QA guys was able to reproduce the issue, I thought it was fixed.
I’ll look up the case.
Thank you @xCyborg !
Pedro
Unity STE
@pedro_unity I’m still having the issue in 2018.1 RC1.
Case number is 1000696.
This is the QA message about reproduction:
I tried all possible solutions I read, but still happens.
@pedro_unity I’m still having the issue in 2018.1 RC1.
Case number is 1000696.
This is the QA message about reproduction:
I tried all possible solutions I read, but still happens.
@xCyborg ,
The case you have linked is closed and marked as not reproducible. Are you sure you are referring to the right issue?
Regards,
Pascal
@okcompute_unity Yes I’m sure 1000696, I quoted the response