BDS-7793Players unable to connect to server
We have been running a server for the past few months with very few problems. However, just recently, players have suddenly began being unable to join. When they try to connect, it sits on the generating world screen for a really long time, and then it says "[player] left the game" in the in-game chat. This is affecting multiple users, both those on and off of the whitelist, but the same players are able to join using different accounts on the same device. This occurs seemingly randomly; for example, a player was able to join this morning but is now unable to despite no changes to the server configuration.
On the console, it registers that the player has joined, however this doesn't come up in-game.
This issue has now started to affect other servers on the same machine.
Created Issue:
Players unable to connect to server
We have been running a server for the past few months with very few problems. However, just recently, players have suddenly began being unable to join. When they try to connect, it sits on the generating world screen for a really long time, and then it says "[player] left the game" in the in-game chat. This is affecting multiple users, both those on and off of the whitelist, but the same players are able to join using different accounts on the same device. This occurs seemingly randomly; for example, a player was able to join this morning but is now unable to despite no changes to the server configuration.
On the console, it registers that the player has joined, however this doesn't come up in-game.
We have been running a server for the past few months with very few problems. However, just recently, players have suddenly began being unable to join. When they try to connect, it sits on the generating world screen for a really long time, and then it says "[player] left the game" in the in-game chat. This is affecting multiple users, both those on and off of the whitelist, but the same players are able to join using different accounts on the same device. This occurs seemingly randomly; for example, a player was able to join this morning but is now unable to despite no changes to the server configuration.
On the console, it registers that the player has joined, however this doesn't come up in-game.
This issue has now started to affect other servers on the same machine.
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[MCQA] Kinga Izdebska](../../../data/avatars/users/18949.svg){kind=small}
Thank you for your report!
However, this issue is Incomplete.
Your report does not contain enough information. As such, we're unable to understand or reproduce the problem.
There could be any number of causes for this issue but its impossible to narrow down based on the information you have provided.
For example, Windows 10 has a "quick edit" mode in command prompt and powershell that pauses the command window (and any processing of that service). If, when your server is no longer contactable, the title bar for the BDS server shows "Select #######" (where ### is the path to your EXE) instead of just the path, this is a Windows feature.
Alternatively, another user has reported connectivity issues under BDS-7793 but I've been unable to reproduce, more information such as whether this happens with a brand new world or just your existing world may help narrow it down.
You are welcome to create a new ticket about your issue with more detailed information.
However, please review the Issue Guidelines before writing a new bug report.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
We'll need more information to try and confirm this. Details about the OS you're running on are crucial.
I'm not able to reproduce this on a vanilla install, have you tried anything like generating a new world and seeing if it affects that? Checking server resource utilization? If on an external host, check that uploading your world to a different host reproduces the same problem? Time drift has also caused inabilities to connect for a number of players.
In general these kinds of issues are usually technical rather than being a bug.
We're running it on Windows 10, version 1.16.1 - we've got multiple servers hosting from a singular machine, and players are able to connect to the other servers even if joining to one doesn't work.
The server has plenty of spare resources, it's definitely not anything to do with that.
I would suggest updating the server to 1.16.10 as 1.16.1 is now outdated. Just to confirm though, is this a Bedrock Dedicated Server?
Unfortunately, without being able to reproduce the issue there isn't much I can do. This issue doesn't occur with a vanilla BDS install so my guess would be there is an outside trigger, whether that be corruption of the player data, a player with a modified client etc.
It is a Bedrock Dedicated Server - I doubt it's anything on the player's end as they are able to join other servers running on the same machine, or join to the same server through a different Xbox Live account.
I'll try updating it now and see if it helps with the problems.
Updating the server version did not help with the issue, and it has now started to affect other servers running on the same machine.
I'm still not able to produce this on any of my servers nor have any other reports come in for the issue which, while I understand you don't agree, points to a config/technical problem.
I have submitted a report that covers non-whitelisted players not getting an error when trying to log onto a whitelist enabled server (
BDS-8262) but that doesn't cover the scenario where you mentioned they have been whitelisted. Unless of course the username you whitelisted wasn't capitalized correctly.Unfortunately without the ability to reproduce the issue, and with no other instances of the problem coming in, there's nothing we can escalate to the devs right now. It would be like giving a mechanic a fleet of cars and telling them one doesn't turn on, but only sometimes and not telling them which one.
Is this still an issue in the latest version (1.17.11)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki