BenK885
Comments
One additional observation:
With BDS 1.26.40.8 on the same host, the main BDS instance using the standard ports 19132/19133 is still detected correctly by GameDig/Uptime Kuma.
Only the second BDS instance using the non-standard ports 19142/19143 is affected. Both instances are running the same BDS version on the same host.
I agree that the client could be involved. However, I cannot test the current client with BDS 1.26.23.1 because the versions are incompatible.
The second instance uses different (non-standard) ports because two BDS instances are running on the same host and IP address. Therefore, different ports are required — not to hide the server.
Downgrading the second server from Bedrock Dedicated Server 1.26.40.8 to 1.26.23.1 immediately restores client connectivity. No other changes were made.
Update
The issue is still present with Bedrock Dedicated Server 1.26.40.8.
The behavior has changed slightly:
When attempting to connect to the second server instance, the Minecraft Bedrock client now times out instead of reporting
InitialConnection-13.The server starts successfully and listens on the configured ports.
The issue remains reproducible under the same conditions described above.
Still relevant in Bedrock Dedicated Server 1.21.111.1 (Linux).
When default-player-permission-level=visitor is set, new players join as members if the world is in Creative mode, but correctly as visitors in Survival mode.
Seems like the property is ignored when gamemode=creative.
Tested on a clean, freshly generated world.
No playerdata or permissions were previously stored.
Update:
The issue is still present with BDS 1.26.51. Clients connecting to the second instance on ports 19142/19143 still time out.
The current iOS client reports:
Prerequisites-32Client version: 1.26.51
The main BDS instance on the standard ports 19132/19133 continues to work normally.