-
Bug
-
Resolution: Incomplete
-
None
-
1.17.40
-
None
-
Unconfirmed
I am running 1.17.41.01 and ran into additional ports being occupied causing me trouble a few hours ago. I have been running a setup that automatically checks for and applies updates every night, so I am not sure when this showed up, but I saw it first last night. I run 3 instances on a single beefy VM, and have server.properties configured to use ports 19142, 19152, 19162 respectively. They all work fine, as they do listen on that port. However, the server also tries to listen on the default port of 19132, and if that port is not available then it picks another (seemingly random) port. Eg Now one instance is listening on: 19142, 19143, 39348, 58651 and the other instance is listening on: 19152, 19153, 52574, 35556
Reproduce steps.. spin up Ubuntu VM, install 1.17.41.01 of BDS, run 2 instances on non-default ports, look at console for ports it’s listening on.