I'm behind a corporate firewall and I'm having trouble installing Unity on Ubuntu 18.04. I can access the 3 locations listed here: https://docs.unity3d.com/Manual/upm-network.html packages.unity.com download.packages.unity.com upm-cdn.unity.com (or upm-cdn-china.unitychina.cn for locations in China) I've also set up the SSL certificates. Meanwhile, there doesn't seem to be much available information for debugging. Is there a flag that can be used with AppImage to get more information? Is there any way to manually install a linux Unity editor? I don't see that as an option from the Archive downloads. Thanks!
I've discovered this thread here for standalone installers. https://forum.unity.com/threads/unity-on-linux-release-notes-and-known-issues.350256/page-2 After setting proxy information in .wgetrc I could download the rest of the installer. However, I don't think the package manager has access to the items it needs. SSL certificates still seem to be an issue.
Should I interpret this as corporate environments are unsupported? https://forum.unity.com/threads/network-configuration.590470/
Hello @crukas , Can you be more specific on the error you are getting when trying to install an editor? You need to set your environment variables correctly : HTTP_PROXY and HTTPS_PROXY (the link should be http not https), and make sure you are not behind a firewall. You can send a bug report through the hub so that we can investigate further your issue.
@safaGH I am behind a corporate firewall and bluecoat proxy. The necessary ports were opened for the UnityHub application. I am unable to install Unity editors with the hub (there are no errors displayed though). The Unity Hub sign in window is non-functional. Upon opening it immediately closes. There are no errors. The UnitySetup-2018.3.0f2 and UnitySetup-2019.1.0f2 both worked upon setting the proxy information in my .wgetrc file and http_proxy in my .bashrc file. The Unity Editor runs. We have also made SSL certificates work for the Package Manger (I need to discuss with internal IT what changes they made, as this was non-functional earlier). In general though, if errors were a little more verbose I think this process might be easier.
@crukas, We are working on improving the error handling and the issues communication to the user. For the network issue, you may need to whitelist some urls if you are behind a firewall : HTTPS://core.cloud.unity3d.com HTTPS://accounts.unity3d.com HTTPS://api.unity.com HTTPS://license.unity3d.com HTTPS://id.unity.com HTTPS://id.unity.com/organizations HTTPS://activation.unity3d.com HTTPS://license.unity3d.com HTTPS://api.unity.com This is a long list, you may not need all of it (depends on how you use the hub), and there is a longer list but keep me posted if this workaround fixed your problems.