Bug Using proxy will cause unity hub failed to open.

As title mention, I can not open Unity Hub while I set HTTPS_PROXY and HTTP_PROXY into system variables. Unity Hub could launch, but what it gives me is a dark screen with nothing on it.
Here is my snapshot :

Left is Unity Hub and right is my proxy connections.
Set Clash to direct or proxy has no effort. The only way to open it is remove HTTPS_PROXY and HTTP_PROXY from system variables.

Env:
System : Windows 10 Pro
Proxy Agent : Clash
Unity Hub Version : 3 Beta 5

 

Here is the log file of Unity Hub

 

Dose anyone could help please....

 

In the logs you included, it says it can't connect to the licensing client.

 

Hello,
I have exactly the same problem. Behind a proxy with HTTP_PROXY and HTTPS_PROXY, the window stay black and the logs says the same things. Do you have an idea to resolve the problem?
Thanks

 

Has this been answered yet? As of today, the problem seems to be still present.

 

https://docs.unity3d.com/2020.3/Documentation/Manual/upm-network.html
Hi there! I was having this same issue and some of my colleagues helped me resolve this. The trick I am using is running Unity Hub via a custom .bat file (I named mine unity.bat, but only the file extension is important--call it whatever you like!)
Here is the contents of the .bat file. Be sure to have the path in the last line point to where the Unity Hub .exe is on YOUR machine:

@echo off
set HTTP_PROXY=
set HTTPS_PROXY=
setx UNITY_NOPROXY localhost,127.0.0.1
start "" "C:\Program Files\Unity Hub\Unity Hub.exe"

Screenshot:


If you have admin policies that prevent you from running .bat files or from Running As Administrator, you may find success by:
1. running PowerShell as Administrator
2. cd to where your .bat file is
3. run the .bat from PowerShell. just type .\filename.bat and press ENTER

That's what worked for me! Hopefully this helps

 

Hello i tried this it did not work

 

Oh my god, it worked Collins! I was pulling my hair on that one. I hate Unity hub 3.

 

Me too. Is a nightmare.

 

UPDATE:
I was working with Unity Support and they released Unity Hub v3.0.1 as a fix to this issue. After I updated to Hub 3.0.1 I don't have to run the software via a script or with any additional settings--I can just click the desktop shortcut. Make sure your Hub is up to date and hopefully that solves your issue too

 

I still have the problem with Unity Hub 3.0.1 on Mac with a zscaler proxy

 

Me to, I tried a lot of solution and still can't sign in. help!!!!!!!

 

So many issues so much pain! I'm coming back to Unity with a new PC and again I can't even reliably launch new or old projects. Unity HUB 3 is complete JUNK JUNK JUNK.

*** I'd personally FIRE all of you, YES ALL OF YOU and anyone at Unity who touched any part of Unity Hub 3, yes, just to be sure this cancer does not spread! Its that BAD! The foundation of Unity is quick sand!!

 

same problem here, but I'm using MacOS. Should I give up on Unity and try Godot?

 

wow this is dumb, I cant imagine anything changed since i last loaded unity, tried the bat file and still loads to screen with nothing, on my windows pc, they are just pushing me to linux, my linux unity is fine, and also considering Godot waiting on next alpha of 4 to come out this week, ha scared it into submission, now its working

 

it sometimes happened, not usually . Seems that it's not allowed to run background ?! (after load, it goes as a background item)

 

I found I was able to open the hub and sign in. The trick for me on Windows 10 Pro was a slight change in case on the environment variables. HTTP_PROXY and HTTPS_PROXY must be lower case.

set http_proxy=http://proxyip:proxyport
set https_proxy=https://proxyip:proxyport

I'm still seeing Unsupported `GLOBAL_AGENT.HTTP_PROXY` in the logs and I'm uanble to download the editor within Unity Hub but I can login at least.

--------------------------
--UPDATE FIXED--
--------------------------
In our scenario our proxy is the same for http and https. Turns out the error was due to incorrectly identifying the proxy with https in the https_proxy environment variable. Once this was changed to match the value of the http_proxy environment variable we no longer see the Global Agent proxy error.

set http_proxy=http://proxyiproxyport
set https_proxy=http://proxyiproxyport

I verified with TCPView on windows that all Unity related processes are honoring the proxy settings and we were able to login, license, and download packages without issue. Hope this helps others.
--------------------------

 

Thank you! It's works!