Cloud not loading things

[NuviaNakara]

Describe the bug?

I cleaned my cache and did data repair but my Resonite loads forever when it comes to textures and also trying to spawn stuff from my inventory just doesn't spawn at all or takes many minutes to even load at all. If even.... I am from Germany by the way.

To Reproduce

Currently it does not access the cloud correctly at all. Very often when I try to spawn something out.

Expected behavior

Opening the game should load me into my world with all textures loaded and when I double click something in my inventory then it's being spawned out.

Screenshots

Resonite Version Number

Beta 2024.5.7.505

What Platforms does this occur on?

Windows

What headset if any do you use?

Pico 4

Log Files

DESKTOP-37660UB - 2024.5.7.505 - 2024-05-08 21_38_59.log

Additional Context

No response

Reporters

No response

[Ahtlon]

I'm also from Germany and have the same problem.

Pinging "skyfrost-archive.resonite.com" has a 15% Packet loss rate

$ ping -4 -c 20  skyfrost-archive.resonite.com
PING skyfrost-archive.resonite.com (172.67.131.221) 56(84) Bytes an Daten.
64 Bytes von 172.67.131.221: icmp_seq=1 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=2 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=3 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=4 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=5 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=6 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=7 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=8 ttl=56 Zeit=108 ms
64 Bytes von 172.67.131.221: icmp_seq=9 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=11 ttl=56 Zeit=107 ms
64 Bytes von 172.67.131.221: icmp_seq=12 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=13 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=14 ttl=56 Zeit=150 ms
64 Bytes von 172.67.131.221: icmp_seq=15 ttl=56 Zeit=106 ms
64 Bytes von 172.67.131.221: icmp_seq=16 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=17 ttl=56 Zeit=105 ms
64 Bytes von 172.67.131.221: icmp_seq=20 ttl=56 Zeit=121 ms

--- skyfrost-archive.resonite.com ping-Statistik ---
20 Pakete übertragen, 17 empfangen, 15% packet loss, time 23250ms
rtt min/avg/max/mdev = 104.820/109.248/150.167/10.873 ms

Traceroute doesn't even finish

$ tracepath -4 -m 10 skyfrost-archive.resonite.com
 1?: [LOCALHOST]                      pmtu 1500
 1:  fritz.box                                             0.470ms 
 1:  fritz.box                                             0.430ms 
 2:  [PRIVATE]                          0.487ms pmtu 1492
 2:  [PRIVATE]                          7.061ms 
 3:  nyc-sb6-i.NYC.US.NET.DTAG.DE                        109.942ms 
 4:  80.156.160.213                                      110.991ms 
 5:  if-ae-0-2.tcore3.njy-newark.as6453.net              112.006ms 
 6:  66.198.70.2                                         114.090ms asym.  7 
 7:  172.70.112.2                                        129.197ms asym.  9 
 8:  keine Antwort
 9:  keine Antwort
10:  keine Antwort
     Too many hops: pmtu 1492
     Zusammenfassung: pmtu 1492

[Frooxius]

Why are you pinging skyfrost-archive.resonite.com? This is not used for downloading assets.

When things are loading slow, can you open the "GatherJobs" page in the "Debug" dialog and see how the downloads are progressing there?

[Ahtlon]

Well it was the only address I could find in the Gather jobs tab. A bit closer:

[Frooxius]

Can you try pinging assets.resonite.com?

[Ahtlon]

Not great

$ ping -4 -A  -c 100  assets.resonite.com                              
PING assets.resonite.com (188.114.97.4) 56(84) Bytes an Daten.
64 Bytes von 188.114.97.4: icmp_seq=1 ttl=56 Zeit=120 ms
...
64 Bytes von 188.114.97.4: icmp_seq=100 ttl=56 Zeit=106 ms

--- assets.resonite.com ping-Statistik ---
100 Pakete übertragen, 89 empfangen, 11% packet loss, time 15772ms
rtt min/avg/max/mdev = 105.046/107.855/122.425/3.554 ms, pipe 2, ipg/ewma 159.317/106.266 ms

[NuviaNakara]

[NuviaNakara]

Here is a fresh ping.

[Banane9]

Fellow German here, the ping to assets.resonite.com is pretty consistent around 107ms ... except for the 12% of attempts with no response.

Ping-Statistic for 188.114.97.3:
    Packets: Sent = 100, Received = 88, Lost = 12
    (12% Loss),
Rough Times in Milliseconds:
    Minimum = 105ms, Maximum = 112ms, Average = 107ms

For comparison, pinging google.com gets an avg. of 18ms with zero loss.

[pingex]

Hello

It appears customers of Deutsche Telekom are affected by a routing issue in which the traffic meant for Cloudflare (which serves Resonite's assets) is sent to Ashburn, US (via NTT) instead of a local routing point.

The packet loss might be a side effect of having an the traffic of potentially the entire country down to a small pipe.

All that people can do right now is wait for the Deutsche Telekom NOC to have their hands on the issue.

FYI I am not affected here in France (ping to assets.resonite.com <20ms).

[Frooxius]

Hmm this is unfortunate, but it sounds that this is out of our hands right now?

I am currently in Czechia and I get good ping and download speeds.

If you're able, can you test with VPN (e.g. VPN to nearby European country) and test with that?

[ProbablePrime]

Hello, could the maintenance Cloudflare is doing contribute to this?

It looks like that should only affect Rio de Janeiro, but perhaps there's a compounding factor.

[pingex]

Hello, could the maintenance Cloudflare is doing contribute to this?

It looks like that should only affect Rio de Janeiro, but perhaps there's a compounding factor.

It might be due to some convoluted factors, but I honestly don't believe it.

I rather think this a long standing issue for Telekom users, especially since multiple people had been complaining about this on Twitter: https://twitter.com/timodoh/status/1786484594671247835 https://twitter.com/haexler/status/1788511501495484806 (3 hours ago) https://twitter.com/EinmaligBefasst/status/1788194625267650804 (yesterday) https://twitter.com/boxesofkittens_/status/1783936982281826526 (end of april)

Anyway, right now I can only advise users to seek and use a VPN with an egress in Europe, which would change their routing points and allow them to get better peering points. Alternatively, if we get to know the real IP behind assets.resonite.com, people can change their C:\Windows\System32\Drivers\etc\hosts file and hardcode it into the file to bypass Cloudflare completely.

What Resonite can do to work around is adding some logic to probe the best CDN or server to pull assets from, but I don't think it's currently worth the effort for a small bunch of people with a sporadic issue to a specific content provider.

If you're able, can you test with VPN (e.g. VPN to nearby European country) and test with that?

I am working with @NuviaNakara to try this out.

[pingex]

Following up on this, I can confirm using a France-based VPN solved all Resonite issues. It even sped up assets loading. So, german players who also are Telekom customers would need to use a VPN until the provider solves their issues with Cloudflare. This may or may not take time depending on how they consider the issue.

[Frooxius]

Alternatively, if we get to know the real IP behind assets.resonite.com, people can change their C:\Windows\System32\Drivers\etc\hosts file and hardcode it into the file to bypass Cloudflare completely.

Unfortunately you can't bypass Cloudflare for this, because the assets are hosted on Cloudflare itself. We are using their R2 storage system.

It seems that assets.resonite.com resolves to a different IP though depending on location. Mine (Czech Republic) resolves to: 188.114.97.9

Can you try pinging that one? See if using that one helps?

[pingex]

Unfortunately you can't bypass Cloudflare for this, because the assets are hosted on Cloudflare itself. We are using their R2 storage system.

Alright, I was not aware of this.

It seems that assets.resonite.com resolves to a different IP though depending on location. Mine (Czech Republic) resolves to: 188.114.97.9

Over location-dependent IP resolution, Cloudflare employs IP anycasting, which makes you reach the closest node available holding that IP, as multiple nodes are holding it across the world.

I got a ping reply from 188.144.97.9 with a latency very close to the last router of my ISP, which means the closest CF node to me is in Paris. I am pretty sure a traceroute to that same IP would show you a node closer to you than Paris is.

I don't have access to a computer behind Telecom right now, however @Ahtlon mentionned a latency >100ms to 188.114.97.4 via Telekom (I assume) as it lands on a US node (because of their broken routing) and despite its number being very close to the one you suggested. I personally get the same latency (lands to Paris) for that particular IP as 188.144.97.9. You can try pinging this one from Czech Republic if you want to compare.