This issue is still a problem and causes severe issues when running multiple servers on the same machine. If BDS finds the default port open it will automatically bind to that port, however, when people try to connect to that port, it will show that the server is popular which makes no sense.
This is a serious issue and needs to be fixed, its a shame this has been open for as long as it has.
EDIT:
Set `enable-lan-visibility=false` in `server.properties`.
Please Fix!
@Mark how does your command work and how can I use it in windows?
@Loren Johnson How would you change the log locations?
How are you going to mark this as a duplicate, when the other post has been open for 7 years?
They are on diffrent ports, also I don’t know what you mean by far enough apart. One is hosted on 19132, and one is on 19134, is that not far enough?
Yes and it’s been happening for a while, I’m pretty sure there has been a open problem for 5 years and still not fixed.
Hey, I'm still having this issue, I'm guessing it has to do with log files on the PC that is stored in the BDS CONTENT LOG LOCATION: `C:\Users\Administrator\AppData\Roaming\logs`.
This issue only occurs when multiple BDS instances are running causing what I'm guessing is a permissions issue for the second bds server.
Please fix this issue, or allow us to change the log file path please!
you have to set op-permission-level in server.properties