stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames

Got many errors like these in our cloud build from yesterday. I assume it's from Unity. Any help?

Code (CSharp):

1. 1: [Unity] DisplayProgressbar: Unity license
2. 2:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
3. 3:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
4. 4:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
5. 5:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
6. 6:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
7. 7:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
8. 8:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
9. 9:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
10. 10: [Unity] An error occurred while resolving packages:
11. 11: [Unity] DisplayProgressbar: Unity license
12. 12:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
13. 13:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
14. 14:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
15. 15:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
16. 16:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
17. 17:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
18. 18:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
19. 19:   stack: 'Error: Hostname/IP doesn\'t match certificate\'s altnames: "Host: staging-packages.unity.com. is not in the cert\'s altnames: DNS:*.bintray.com, DNS:bintray.com"\n    at Object.checkServerIdentity (tls.js:223:17)\n    at TLSSocket.<anonymous> (_tls_wrap.js:1111:29)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:639:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:469:38)',
20. 20: [Unity] An error occurred while resolving packages:
21. 21: publishing finished successfully.
22. 22: Finished: FAILURE

 

Me too, dont find a solution

 

Yeah. And there is no reply from Unity. Maybe they #WorkFromHome

 

Well, they still release new versions of engine, so I guess they're still up and running even from home.
Same problem though with my cloud build I hope they'll resolve that within the next days :/

 

Please check your manifest file and make sure that it does not reference

staging-packages.unity.com

- this package registry was disabled some time ago and should not be used. If you are able to reproduce this reliably with a clean manifest then please contact support so that we can investigate further.

 

Urh. Thanks, but by removing the line, I have that now on startup :/.
What do I do ?

Just in case :
- Cloud build manually setup to build for my version Unity 2019.2.21f1
- Not planning on getting anytime soon on 2019.3, only 2019.4 when released.


I also tried to put "registry": "https://packages.unity.com" rather than nothing but that's no better.

Current state of manifest

Code (CSharp):

1. {
2.   "dependencies": {
3.     "com.unity.2d.sprite": "1.0.0",
4.     "com.unity.2d.tilemap": "1.0.0",
5.     "com.unity.analytics": "3.3.2",
6.     "com.unity.cinemachine": "2.3.4",
7.     "com.unity.package-manager-ui": "2.2.0",
8.     "com.unity.postprocessing": "2.2.0",
9.     "com.unity.recorder": "2.0.2-preview.2",
10.     "com.unity.remote-config": "0.3.0-preview.4",
11.     "com.unity.render-pipelines.lightweight": "6.9.1",
12.     "com.unity.shadergraph": "6.9.1",
13.     "com.unity.textmeshpro": "2.0.1",
14.     "com.unity.timeline": "1.1.0",
15.     "com.unity.ugui": "1.0.0",
16.     "com.unity.vectorgraphics": "2.0.0-preview.4",
17.     "com.unity.modules.ai": "1.0.0",
18.     "com.unity.modules.androidjni": "1.0.0",
19.     "com.unity.modules.animation": "1.0.0",
20.     "com.unity.modules.assetbundle": "1.0.0",
21.     "com.unity.modules.audio": "1.0.0",
22.     "com.unity.modules.cloth": "1.0.0",
23.     "com.unity.modules.director": "1.0.0",
24.     "com.unity.modules.imageconversion": "1.0.0",
25.     "com.unity.modules.imgui": "1.0.0",
26.     "com.unity.modules.jsonserialize": "1.0.0",
27.     "com.unity.modules.particlesystem": "1.0.0",
28.     "com.unity.modules.physics": "1.0.0",
29.     "com.unity.modules.physics2d": "1.0.0",
30.     "com.unity.modules.screencapture": "1.0.0",
31.     "com.unity.modules.terrain": "1.0.0",
32.     "com.unity.modules.terrainphysics": "1.0.0",
33.     "com.unity.modules.tilemap": "1.0.0",
34.     "com.unity.modules.ui": "1.0.0",
35.     "com.unity.modules.uielements": "1.0.0",
36.     "com.unity.modules.umbra": "1.0.0",
37.     "com.unity.modules.unityanalytics": "1.0.0",
38.     "com.unity.modules.unitywebrequest": "1.0.0",
39.     "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
40.     "com.unity.modules.unitywebrequestaudio": "1.0.0",
41.     "com.unity.modules.unitywebrequesttexture": "1.0.0",
42.     "com.unity.modules.unitywebrequestwww": "1.0.0",
43.     "com.unity.modules.vehicles": "1.0.0",
44.     "com.unity.modules.video": "1.0.0",
45.     "com.unity.modules.vr": "1.0.0",
46.     "com.unity.modules.wind": "1.0.0",
47.     "com.unity.modules.xr": "1.0.0"
48.   }
49. }

 

You'll need to find the replacements for those versions in the main production package registry. Everything that was previously hosted in staging-packages should be hosted in production but that doesn't seem to have happened in this case. What I would suggest doing is using that registry line you mentioned and deleting the two offending packages from your manifest file. After doing that and loading Unity you should be able to find and install the valid production versions of these packages using Window -> Package Manager.

You mentioned that you didn't want to update until 2019.4 comes out which is definitely fair and I commend you for that but that would also probably resolve this. You're probably right about wanting to avoid 2019.3 but 2019.2 is pretty stable at this point and so could be a pretty safe update if you wanted to try that out - which might be important if the valid production version is older than the one you're referencing here and you were depending on features that were only available from the staging registry.

 

..But as I said, I'm using 2019.2.21f, I have been for a big month and I wasn't having problem with my cloud build until yesterday ^^'.
I didn't took the time to recheck yet, but some of those doesn't even have production version in 2019.2 :/

 

Ah yeah I misread sorry. 2019.3 is getting pretty stable and the upgrade gap between .3 and .4 should be pretty minimal because of the development process - .4 is effectively the exact same version as .3, it's just a designation that happens once we decide that .3 has reached a point where we are confident about stability and feature set. But yes holding off for the LTS version is still probably wise.

In theory all staging-packages versions should have a version available in production but it doesn't seem that has happened here. If you take a look at which packages are unavailable in production then I can talk to the teams involved about whether they are able to add a supported version for 2019.2.

As far as the staging-packages registry goes, it's been deprecated for many months now. However the SSL certificate expired for this domain over the weekend which is why it has stopped functioning in Unity Cloud Build. I haven't tested this but I'm pretty sure if you installed a new version of Unity or set up your project for a new developer then they would also be unable to connect to staging-packages, it's only cached data that allows you to still connect locally. However, the backend is planned for deletion in the very near future and so one way or another all users will have to migrate to the production registry.

 

I see :/
Stopping updating version and truly forcing myself to wait is like the biggest learning I've made in my 5+ years of Unity ^^. I guess most people that got irritated have had issues with the way Unity changed its communication in the last years, and how the definition of a public beta changed.... But that's another subject

Well then, if you can help me to get the word to the team... ^^
Regarding packages, production ready are the one with the 'verified' tag in 2.2.0 version of package manager right ?
Hopefully, most of them are verified.

Then for the rest (in my case) :
-Cinemachine doesn't have any production ready, whether It's 2.3.4 or 2.3.3, they're not in preview either but not tag (I'm using 2.3.4). I don't have the impression that it's a problem though ? it seems to work
-PostProcessing I'm using 2.2.0, it's not verifed nore preview, 2.1.7 is verified, so I guess I have to revert to 2.1.7
-Remote config is only preview (0.3.0 latest) but not that important.
-UnityRecorder is all preview apart from 1.0.1, it's like...old and It would be hard to revert (i'm using latest preview 2.0.2 , 2), but I guess I have no choice either but to revert too

I guess the ones with only preview like remote should be then..Removed in 2019.2 ? I mean people that use them will now be stuck if they want to use that with cloud build in 2019.2.

In any case, if users starts to have to deal with problem like that for 2019.2 when they do not use verified package, there's better be an update to package manager to warn users about the issue.

 

Hm. I removed the incriminated packages (recorder or 2.2.0 post processing).
Which made new packages version available ?...
Cinemachine 2.5.0. nice, still not verified tho
Hm..

 

Yeah production ready packages should have the verified tag however anything that was only available on the staging-packages registry is by definition not verified no matter what it says. This kind of confusion is a big part of why staging-packages got deprecated in the first place.

It's a bit odd that you can't see the new packages without deleting the old references but as long as it works I'm happy! From what I could see (when running 2019.2.15f1 locally) there is a valid upgrade available for all of those versions.