View Issue Details

IDProjectCategoryView StatusLast Update
0016497MediaMonkey 5Synchronizationpublic2020-04-22 02:45
PriorityurgentSeverityminorReproducibilityhave not tried
Status closedResolutionreopened 
Product Version 
Target VersionFixed in Version5.0 
Summary0016497: Do not allow MM5/MM4/MMS on same PC use same Port for DLNA/Sync
DescriptionIf MM4 and MM5 Uses same Port for library sharing they both fail and MMA Can't sync.

We should add at least MM detect other MM instance uses same port and warn user.
Steps To Reproduce1. Set for example bit torrent Application (Any application that listens port can be used, in user case he had MM4 started) to use same port as MM DLNA server
2. Make sure MM5 is closed
3. Start bit torrent application
4. start MM5
5. Use MMA to access MM5 over UPnP -> Fail
6. Close MM5
7. Close Bit torrent app
8. Start MM5
9. Use MMA to access MM5 over UPnP -> All OK
TagsNo tags attached.
Fixed in build2240



2020-04-07 10:05

developer   ~0057507

Last edited: 2020-04-07 20:02

View 3 revisions

I think that the real solution is not allowing to run the two instances simultaneously (like we do in MM4).

i.e. if there is '[x] Allow just one instance of MediaMonkey' checked then MM5 shouldn't be allowed to run when MM4 is running and vice-versa.


2020-04-07 11:36

developer   ~0057509

Last edited: 2020-04-07 11:45

View 4 revisions

I am not sure that it is the right solution, especially as both MM4 and MM5 can coexist together as apps.

maybe simple on start probe would be simple just before MM creates/init DLNA server or when DLNA server starts Listening to a port and gets some error code.

Simple return from tcpclient like would be enough.
Or maybe something like this examples could help or or


2020-04-07 19:42

developer   ~0057520

Last edited: 2020-04-07 20:04

View 3 revisions

Sure, we could show a warning that another instance of MM is running, but is this really needed espacially when user set '[x] Allow just one instance of MediaMonkey' ?
I would say that MM5 shouldn't be allowed to start in the first place.

Assigned to Rusty for review.
@Rusty: If you think that a warning suggested by Peke makes sense then suggest a wording.


2020-04-07 20:02

developer   ~0057522

This issue do not have any issues with multiple MM instances started, but with fact that two instances of MM or any other application can already open port that MM is using for DLNA and Sync and MM do not check if port is open or not just tries to open port.

We should implement open port checks like I pointed at 0016497:0057509 so that MM no matter what app is listening that port MM know that and do not assign port and show warning that DLNA/Sync will not be available as other app (no matter if MM4/MMS/MM5/WMP/... already uses that port).

As for multiple instances started I am Ok that multiple same MM5 exe are not executed, but that is completely different issue.


2020-04-07 20:14

developer   ~0057523

Last edited: 2020-04-07 21:51

View 5 revisions

Note that it is not about opening port, but using ports. i.e. we would need to check whether another app is using the port which might not be reliable and could slow server start.


2020-04-07 21:43

developer   ~0057530

Last edited: 2020-04-08 21:05

View 4 revisions

Implemented the warning in 2240.

The current message is
'<servername> server could not start, port <number> is already in use'

@Rusty: review the wording


2020-04-08 08:31

developer   ~0057546

Last edited: 2020-04-08 21:08

View 3 revisions

Re-opened as thinking about it better wording would be:

'"<servername>" media server could not start, port <number> is already in use. Check whether another instance of MediaMonkey isn't already running or change the port in Options > Media Sharing'
=> Fixed in 2240



2020-04-08 21:00

developer   ~0057563

Verified Functionality in 2240

Assigned for feedback to Rusty on wording/clarification.


2020-04-08 21:35

administrator   ~0057568

"Media server '<servername>' could not start: port <number> is already in use.
Check whether another instance of MediaMonkey is already running or change the port # in Options > Media Sharing."


2020-04-08 22:13

developer   ~0057569

Wording updated in 2241


2020-04-22 02:45

developer   ~0057678

Verified Wording in 2242