Cesium3DTileset not rendering in packaged build Ue5.3.2 with Cesium 2.2

When I am in play mode in the editor the tiles render fine. The moment I package a build and try to load the level with the cesium tile it is just blank.

Here is what I found in the logs:

[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: request failed, libcurl error: 60 (SSL peer certificate or SSH remote key was not OK)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 0 (  Trying 18.160.213.44:443...)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 1 (Connected to api.cesium.com (18.160.213.44) port 443 (#0))
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 2 (ALPN: offers http/1.1)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 3 (TLSv1.3 (OUT), TLS handshake, Client hello (1):)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 4 (TLSv1.3 (IN), TLS handshake, Server hello (2):)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 5 (TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 6 (TLSv1.3 (IN), TLS handshake, Certificate (11):)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 7 (TLSv1.3 (OUT), TLS alert, unknown CA (560):)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 8 (SSL certificate problem: unable to get local issuer certificate)
[2023.12.14-21.39.05:833][267]LogHttp: Warning: 00000234AE6D4BD0: libcurl info message cache 9 (Closing connection 0)
[2023.12.14-21.39.05:838][267]LogCesium: Error: [2023-12-14 21:39:05.839] [error] [TilesetContentManager.cpp:825] An unexpected error occurred when loading tile: Request failed.

Edit: So I tested the build in a different environment and the Cesium Terrain shows up on that one but not on the computer that I need it to work on. I am not sure where to look to find the root cause…

Those look like a problem with the network. Perhaps the problematic system needs to use a proxy server to access the internet? Unreal Engine unfortunately does not use the default Windows proxy settings by default (are you even on Windows? You haven’t said.)

Some users have been able to get Unreal Engine to use a proxy by setting an environment variable:

We just set up a new environment. Somehow the server’s SSL certificate became corrupted so it was easiest just to start a new instance.