Unclear singular experience player drop from cause "ID=17. Connection attempt failed."

Reproduction Steps
Hoping there’s internal Roblox logs for this, as it is no longer occurring. My intent of reporting this is to make sure it is identified and to make sure this does not happen to my experience or other experiences in the future.

Between 11:00 PM and 11:59 PM EST on 01/09/22, it was impossible to join or teleport within The Day the Noobs Took Over Roblox 2.

I don’t believe this was a DDoS attack and I am pretty certain the player drop was not from players going to sleep. I received several user reports about the inability to successfully join + teleport. I can correlate this with an abnormal player count dip on numerous trackers (Roblox Creator Dashboard, Roblox Developer Stats, Rolimons) for the affected hour. Without server logs though, all my guesses are speculation.

Expected Behavior

  • Players are able to join and teleport within my experience
  • Players are able to join and teleport within other experiences
  • My player count stays at its expected number for the time of day (it doesn’t massively deviate from the usual trend)

Actual Behavior

  • Players are unable to join my experience - they receive a connection failed error with the ID of 17
  • Players are unable to teleport within my experience
  • My player count drops from ~50 players to ~5 players in the span of ~10 minutes
  • Players are still able to join and teleport within other experiences at this time, meaning this server issue was likely isolated

Workaround
Time. For some reason this error only lasted for about an hour. My player count returned to the expected number and I stopped receiving reports.

Issue Area: Engine
Issue Type: Connectivity
Impact: Very High
Frequency: Very Rarely
Date First Experienced: 2022-01-09 23:00:00 (-05:00)
Date Last Experienced: 2022-01-09 23:59:00 (-05:00)

13 Likes

This error is still going, at least for me.
Additionally, it is actually occurring platform-wide and not only a specific experience.

5 Likes

Doesn’t look like it affected my experience this time. Unless you’re referring to a platform-wide player drop, it looks like it may only affect various experiences (or maybe servers/regions) relatively randomly?

Would you mind linking your affected experience for context? Also about what time did it start?

2 Likes

Guessing the server cause it may not be a bad guess. However, I may not be thinking it would be a specific experience, I’d rather think it would be the server region that could potentially have the error. It is unclear what would be the root cause of it.


I mainly got the error from this game join any server for the first time is fine, mostly getting the error if they were to teleport me to another server, especially for this experience as there are different maps that are based on servers, not place.

This is what could’ve happened when changing servers in that experience.


It is hard to believe it would be the server region, as this happened frequently not happening straight away, it may also be because of Roblox launcher is having a hard time connecting with the server origin.

5 Likes

Can confirm. It has been happening in my experience and causes huge player drops, unsure whatever the cause is, but I have it had happen three times in public servers so far.

5 Likes

Would you be able to post a link to your experience and the rough times for when this occurred for you?

1 Like

Hi, absolutely.

Experience:
https://www.roblox.com/games/6562263018/FREESTYLIN-13-Emote-Legacy#

These issues happen roughly around the 50-59 minutes into the hour. The times I experienced all 3 were around:

  • (7:50-7:59 / 8:50-8:59 / 9:50-9:59)
4 Likes

Happening in FE2CM

2 Likes

Figured i’d bump this, it’s still happening.

Following screenshots aren’t mine and are from users;

image


5 Likes

Users from my game are also reporting having this issue
(image is from a player)

4 Likes

We are still experiencing this in Splash. To be clear, the ID=17. Connection attempt failed.

It seems to be caused by the servers with 0 players in them that don’t seem to go away unless we manually kill them.

I have attached a screenshot from a player.

5 Likes

This issue is currently happening in Starscape as well, with significantly increased frequency today. Huge negative to our player experience. Investment in reliability should be Roblox’s top priority.

5 Likes

Presumably had another bout of this today for TDTNTOR 2 for about an hour. These occurrences really make it difficult to keep a concurrent player count.


Would love clearer timezones + granularity for these metrics tbh.

2 Likes

I believe me and some others found the issue behind these crashes:

Games that explicitly use a lot of animations suffer currently from a high rate of server crashes as animations do not get unloaded on stopping a track on the server, which leads to animation data stacking up and after some time crashing the server (and potentially client). Specifically games with over hundreds of socialising actions and dancing choreography are suffering a lot from this issue.

I’ve reported this issue to people who have direct contact to roblox in hopes of this issue being addressed, as it’s been almost a week with this issue standing. There have been hourly crashes I cannot prevent, worst part being left out with no alternatives or workarounds.

I expect reliability from roblox when it comes to such game-breaking issues, even if there aren’t many games that are fully dependant on animations some of us still need the sufficient support.


obviously, I could be fully wrong about the above being reasoning for the server crashes, but considering @lexandstuff’s game “Splash” is affected (which is as far as I know using a lot of animations) and aswell as my game (which contains 900+ individual animations players can use at any moment), i’m very certain this could be the issue.

3 Likes

Interesting theory! Seems plausible. Hopefully Roblox staff will be able to weigh in.

FWIW my experience does not utilize large quantities of animations. Maybe it could still accumulate via the default player animation scripts. Players constantly visit the root place, so an animation memory leak from those scripts would actually make a lot of sense.

Both times for me have been off-peak hours, when most servers have already naturally closed - meaning the default animation scripts could overload the small number of servers (or server singular) more easily. :thinking:

3 Likes

Unfortunately, in our case it’s happening on our Portal server, which is simply a landing place with a full screen gui that directs people to our other places. There should be very few animations playing on this server. Players should only be spending 10-20 seconds in the place, so potentially something to do with default player animations accumulating as @cloakedyoshi mentioned.

There’s another thread that matches with the issue we’re experiencing: https://devforum.roblox.com/t/roblox-servers-that-cannot-be-joined

My guess is there’s a few different reasons for the ID=17 bug.

3 Likes

Hello, is this issue still occurring for you ?

3 Likes

I have personally not experienced it or had it reported to me since January 24th. Unsure if it is resolved. It appeared to be something with a specific “corrupt” server for an experience.

2 Likes

I deeply apologise for the bump, but I just wanted to inform you that it is still occurring, as shown here:
image

4 Likes

If it helps in the meantime, you can solve this bug by manually shutting down that server. It may happen again in the future, but it’ll stop it for the time being.

2 Likes