When you define environment variables from a command line, the values don’t persist across sessions. A process can use those environment variables if it’s launched from the same session, but after you end that session, you must define the values again.
Administrators can set environment variables at the operating system level. If that’s not an option, you can create a command file to set environment variables and launch a Unity application, such as the Hub, from the same session. This executable file becomes a reusable method for opening the Unity Hub with the environment variables required by your environment.
Important: After the command file is created, be sure to always launch the Unity Hub using that file, instead of standard methods, such as the Start menu (Windows) or the Applications folder (macOS).
Decide which environment variables you need to set, and include only the required environment variables:
HTTP_PROXY and HTTPS_PROXY environment variables to identify your web proxy. For more information, refer to Use environment variables to identify your web proxy.NO_PROXY environment variable.NODE_EXTRA_CA_CERTS environment variable. For more information, refer to Trusting the web proxy security certificate.If you’re setting the HTTP_PROXY and HTTPS_PROXY environment variables, make sure you use the proper value to include or exclude authentication information.
These instructions create an executable file named launchUnityHub.cmd.
Close the Unity Hub, if it’s running.
Open a text editor such as Notepad.
Enter the following text, adjusting as necessary:
@echo off
REM *** NOTE: Add the next 3 lines only if you’re not using Automatic Proxy Configuration
set HTTP_PROXY=http://<username>:<password>@<proxy_name_or_IP_address>:8080
set HTTPS_PROXY=http://<username>:<password>@<proxy_name_or_IP_address>:8080
set NO_PROXY=<licensing_server_name_or_IP_address>
REM *** NOTE: Add the following line only if your web proxy uses SSL inspection
set NODE_EXTRA_CA_CERTS=<path_to_pem_file>
start "" "C:\Program Files\Unity Hub\Unity Hub.exe"
Note: If there are spaces in the path, you must use double quotes around the path to the program.
Save the file to a location where you can find it (such as the Desktop), and make sure the file has the .cmd extension (for example, launchUnityHub.cmd), not launchUnityHub.txt or launchUnityHub.cmd.txt.
Double-click launchUnityHub.cmd to launch the Unity Hub with the required environment variables intact.
The Unity Hub passes these environment variables to any process it spawns, such as the Unity Editor.
These instructions create an executable file named launchUnityHub.command.
Close the Unity Hub, if it’s running.
Open a Terminal window.
Run the following command, adjusting as necessary:
echo '#!/usr/bin/env bash
# *** NOTE: Add the next 3 lines only if you’re not using Automatic Proxy Configuration
export HTTP_PROXY=http://<username>:<password>@<proxy_name_or_IP_address>:8080
export HTTPS_PROXY=http://<username>:<password>@<proxy_name_or_IP_address>:8080
export NO_PROXY=<licensing_server_name_or_IP_address>
# *** NOTE: Add the following line only if your web proxy uses SSL inspection
export NODE_EXTRA_CA_CERTS=<path_to_pem_file>
nohup "/Applications/Unity Hub.app/Contents/MacOS/Unity Hub" &>/dev/null &' > launchUnityHub.command
Note: If there are spaces in the path, you must use double quotes around the path to the application.
Run the following command to make launchUnityHub.command executable:
chmod +x launchUnityHub.command
Move the launchUnityHub.command file to a convenient location (for example, the Desktop), if you prefer.
Double-click launchUnityHub.command to launch the Unity Hub with the required environment variables intact.
The Unity Hub passes these environment variables to any process it spawns, such as the Unity Editor.