Cory West
Assigned
Comments
This is starting to smell like a threading issue / race condition. I hope the team takes it seriously so it gets fixed soon.
False alarm… that second failure was user error. So… to sum up: I had to set lan_visibility to true and add transport=raknet.
And now it won’t connect again. Sigh.
AHH! If I set lan_visibility to TRUE it will allow connections!
Here’s all the steps I’ve tried. There is definitely something broken here.
Set up new vanilla server 1.26.31.1 with new vanilla world on port 19132. Works fine.
Change port of new vanilla server to 19134. Continues to work fine.
Add transport=raknet to my server.properties for my pre-existing server. Load my server with 1.26.31.1 on port 19134. Server loads but clients cannot connect.
Try changing the port to 19132. Server loads but clients cannot connect.
Tried connecting the IPv6 address and port. Client cannot connect.
Apparently I can’t close this… so please ignore it.
Embarrassing user error. Closing.
I was able to resolve this on my installation by setting transport=raknet and enable-lan-visibility=true. (I don’t actually want lan visibility enabled, but unless I set it to true connections can not be made to the server. I use the allowlist to control access so the lan visibility shouldn’t be a problem.)
This is on a commercially hosted bare metal server that I administer with stable networking.