-
Bug
-
Resolution: Incomplete
-
None
-
1.19.70
-
None
-
Linux / docker
-
Unconfirmed
If you set individual ports (e.g. 20132), the server will still use 19132 for lan discovery.
There are multiple work arounds out there. e.g.: not to start the server until the server.properties was modified for the 1st time. This works until you update (in my case from 1.19.70 to 1.19.71), now it is again using 19132 for lan discovery.
[2023-03-18 12:10:21:734 INFO] IPv4 supported, port: 20132: Used for gameplay
[2023-03-18 12:10:22:336 INFO] IPv4 supported, port: 19132 used for LAN discovery
The expected behavior is to use the port from IPv4 from server.properties also for lan discovery instead of falling back to default.
- is cloned by
-
BDS-19399 LAN discovery does not adhere to port configurations.
- Resolved