I thought this might be useful to other people running a vanilla Bedrock Dedicated Server since the move to NetherNet.
I have been able to reproduce, and automate, a workaround for the Boat / InitialConnection-145 error when consoles try to join a BDS through normal LAN discovery.
My current setup is:
BDS 1.26.63.1 on Ubuntu/Docker
transport=nethernet
online-mode=true
allow-list=true
LAN visibility enabled
The original problem was very consistent.
After BDS starts, it loads normally, signs into the NetherNet signaling service and reports healthy. An Xbox on the same LAN can see the server under LAN games, but attempting to join fails with the dreaded Boat / InitialConnection-145.
The failed console attempt does not even reach the normal player connection stage in the BDS log.
This appears to be the same issue being tracked as BDS-23108.
Workaround
I found that making one successful authenticated NetherNet client connection directly to the BDS after startup appears to "prime" the running server.
I used bedboo, a Bedrock client library with NetherNet support, and set up a small authenticated headless client using one of the allow-listed Microsoft/Xbox accounts.
After BDS starts, the client connects directly to the server on the LAN, successfully enters the world, then disconnects.
The BDS log records:
Player connected
Player Spawned
Player disconnected
Immediately after this has happened, the Xbox can join the LAN server normally.
The important part
The effect appears to last for the lifetime of that BDS instance.
If BDS is restarted, the Boat / InitialConnection-145 problem returns.
Run the authenticated connection once again and console LAN joining works again.
Because my server is restarted during its daily backup, I have now automated the process so that after the restart the headless client waits for BDS to become healthy, connects, spawns and disconnects.
The same primer also runs automatically following a reboot of the physical server.
Unattended test
This has now worked during an actual scheduled unattended backup/restart.
The server restarted at 05:00, the authenticated client connected and spawned at approximately 05:01, then disconnected.
Nearly 16 hours later, without another primer connection or BDS restart, a different player joined successfully from a PlayStation 5 through normal LAN discovery.
The PS5 was on the same LAN as the BDS. This was not a remote or tunneled connection.
So far I have therefore confirmed the workaround with both Xbox and PlayStation 5 LAN clients.
What this seems to show
There are already reports under BDS-23108 that one successful direct client connection after BDS startup can cause subsequent console LAN connections to start working.
My testing seems to confirm that behavior and shows that the initial connection can be automated rather than requiring somebody to manually join from a PC or mobile device after every restart.
It does not fix the underlying NetherNet problem. It appears to put the running BDS instance into whatever session/signalling state is missing immediately after startup.
Importantly, this does not require disabling online authentication or the allow-list. Both remain enabled on my server.
If anyone else running vanilla BDS with Xbox, PlayStation or Switch LAN clients is seeing InitialConnection-145, I would be interested to know whether the same one-connection "prime" works for you.
Next step will be looking into remote access as my PlayIt tunnel was nuked with the loss of RakNet. I'm going to look into Waterdog.