# Cesium3DTileset not rendering in packaged build Ue5.3.2 with Cesium 2.2
**URL:** https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731
**Category:** Cesium for Unreal
**Created:** [December 14, 2023, 9:49pm UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731 "2023-12-14T21:49:20Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@TeraDan](https://community.cesium.com/u/TeraDan)
#### Post date: [December 14, 2023, 9:49pm UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731/1 "2023-12-14T21:49:20Z")
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:
```auto
[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…
---
### Author:  [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)
#### Post date: [December 18, 2023, 11:40am UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731/2 "2023-12-18T11:40:47Z")
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:
> [@Error connecting Cesium to Unreal](https://community.cesium.com/t/error-connecting-cesium-to-unreal/12953/8):
>
> We were able to get around this issue by adding system environment variables for HTTP\_PROXY and HTTPS\_PROXY.
---
### Author:  [@TeraDan](https://community.cesium.com/u/TeraDan)
#### Post date: [December 27, 2023, 6:03pm UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731/3 "2023-12-27T18:03:51Z")
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.
---
### Author:  [@dividebylife](https://community.cesium.com/u/dividebylife)
#### Post date: [October 24, 2024, 1:07am UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731/4 "2024-10-24T01:07:30Z")
> [@Error connecting Cesium to Unreal](https://community.cesium.com/t/error-connecting-cesium-to-unreal/12953/8):
>
> ere able to get around this issue by adding system environment varia
> [@TeraDan](#):
>
> 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.
Hi @TeraDan,
Would you mind elaborating? Some of our devs are running into the same issue today, but our project only uses listen servers. When you say “start a new instance”, which server are you referring to?
---
### Author:  [@RoeDan](https://community.cesium.com/u/RoeDan)
#### Post date: [February 16, 2025, 9:16pm UTC](https://community.cesium.com/t/cesium3dtileset-not-rendering-in-packaged-build-ue5-3-2-with-cesium-2-2/28731/5 "2025-02-16T21:16:38Z")
Hi, I moved companies. It’s been so long it may not be relevant now but I believe we were hosting servers with gcloud so when I said, “Start a new instance” I meant cloning our instance and gcloud and moving to the new server.
Something with windows server ssl certificate was wonky.