Joshua Greenlaw

We just experienced the same thing on my server. 

This also started happening on my dedicated server. Version 1.14.32, Ubuntu server x64

Both issues are describing the same issue, as far as I can tell.  Both issues were fairly verbose, but I think they contain the same information. One report should be good. 

Thanks for your response! I've uploaded a zip file with several things.

• SinglePlayer-ConnectCommand.png shows me using the connect command in single player

• SinglePlayer-ConnectSuccess.png is the success message, plus me sending a chat message

• SinglePlayer-WebsocketOutput.png shows the websocket listener I have receiving the message

• BDS-ConnectCommand.png is me trying to use the same command from a BDS instance in game

• BDS-ConnectFailure.png is the failure message that I received

• BDS-Console-ConnectFailure.png shows me trying to use the commands directly from the BDS console

  • Yellow highlight is the command as used previously, with a valid listener address

  • Blue highlight shows the command used with no arguments

• Finally, the MC_WSS folder contains a barebones Node.js application which I used for a websocket listener

My expectation is that on a BDS instance, I should be able to use the connect command to connect to the same websocket listener as in single player. Please let me know if you have additional questions. 

This is also happening on my BDS instance, Ubuntu Server 18.04

Because it might help, code is here: https://pastebin.com/SpJPj6s1

It uses Node.js and MS SQL Server Express, all secrets have been scrubbed. Again, it works in single player, but not in BDS or Realms.

This happens to me on Android as well.

Not sure if it's related or a separate issue, but villagers just sit in water and drown instead of swimming with 1.9. In single player the vibrate up slowly (way slower than they used to swim) but on my server they just sit there and die.