We run an old, but still popular online game built on Unity 4x. We own a lifetime, unlimited pro license for this version of Unity. As of this morning we have been unable to use the Unity 4x editor due to a problem with the license server. Upon starting the editor we get the following error before the editor closes:
“Peer certificate cannot be authenticated with known CA certificates”
Right now this is having a serious negative impact on our business. Please kindly fix the issue ASAP.
I second this request. It’s impacting an ongoing conversion from Unity 4.x to Unity 2022
If anybody is experiencing the same issues we were, I was eventually able to get Unity 4 to open. I disconnected my Internet, removed the Unity 4 file from :/ProgramData/Unity/the_file.ulf, and generated a license request (alf) file.
Reconnected my Internet, then I went to a GitHub project that automates the request and receiving process for licenses easier:
Some knowledge of command-line will be helpful here. I’ve already installed Windows Git with bash support, which allows you to open up a bash terminal by right clicking any open folder and selecting “Open Git bash here”. The more important part is that you’ve got some kind of Linux-style terminal that you can open and run commands like wget or curl. Installing Windows Git is one of the easiest ways that I know to achieve this.
You’ll have to install the latest NodeJS (v20.x, as of this writing) + NPM, preferably through NVM (GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions) which will handle most of the heavy lifting for you. You run an nvm install command with the version, and it automagically install NodeJS and NPM, conveniently.
Install the unity-activate npm module globally (-g) per the GitHub instructions near the bottom of mob-sokai’s GitHub page, and run the command unity-activate path/to/your/file.alf, which is the path to your Unity license request file. It asks for username (your email, actually) and password, then reaches out to the licensing service, authenticates, sends your alf, you eventually get a ulf file back, and it saves that license file to the same location as your alf.
Once again, turn off the Internet, copy and paste that ULF file into :/ProgramData/Unity/the_file.ulf, and restart Unity. You might get a “license is expired”, just click “Reactivate License”, and Unity 4 should start up. I have since tried to activate my Internet connection to see if the licensing sorts itself out, but I think if it ever acts up again, I can just disconnect the Internet to open it, go about my business, and reconnect at the end of the day, worst case scenario. But it flippin’ opens, and that’s all I care about.
I hope this helps somebody else out there. Unity support is horrendously slow right now, and I imagine Unity 4 customers are at the very bottom of their priority list on top of the massive delays.
Works just fine when you reconnect to the Internet, so long as you don’t have to close and reopen it. Or try to open the asset store or tutorials or anything. And you won’t have the “pro” portions. Still, better than nothing.
Everything is very complicated
After a while, I also managed to launch Unity 4 using the yumupdate instructions, but unfortunately the splash screen is not displayed in the PC build
As I mentioned, you won’t have the “Pro” abilities (a splash screen). I needed Unity 4 to open so that I could compare what we had in “old Unity” to what was happening in Unity 2022, since we were forklifting the project to the modern era of Unity and there were a lot of issues during that process that I needed to confirm weren’t issues in Unity 4. Thankfully, I didn’t need (or want) to build anything with Unity 4 anymore.
Good luck with it. Maybe one day some official legacy server will be stood up to assist all of us that shelled out significant amounts of money for those older licenses. Here’s hoping.
@yumupdate The splash screen issue was resolved through a script written by ChatGPT. In the current version of the script, the transition from the splash screen to the first scene is fade, instead of the more familiar transition without it. The text “Trial version” will also appear in the scene. I will solve all the problems further…