View Issue Details

IDProjectCategoryView StatusLast Update
0015541MMW 5Syncpublic2022-09-14 14:32
Reporterpeke Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status feedbackResolutionopen 
Product Version5.0 
Target Version5.2 
Summary0015541: MMS: MM5 do not see MMS on QNAP
Description1. MM5 Do not automatically detect MMS installed on QNAP related to GitHub issue https://github.com/mediamonkeyserver/mms/issues/27

2. If I enter QNAP MMS IP and PORT to Add Servers MM5 tells that can't be reached
Expected: Entering direct URI (as suggested in MMS LOG) in MM5 Add Server to add and query MMS settings

Screenshots and Logs from both MMS and MM5 are uploaded to ftp.
TagsNo tags attached.
Fixed in build

Relationships

related to 0015557 closedLudek MMS: Manually enter MMS address creates double MediaMonkey Server 
related to 0015570 assignedpeke MMS: MMS Settings can't be edited or Viewed or initiate manual check 
related to 0016583 closedLudek More clear setting for manual Add Media Server Dialog 
related to 0016580 closedLudek DLNA: MM5 sometimes fails to see some DLNA Servers 

Activities

Ludek

2019-03-14 12:13

developer   ~0052967

Last edited: 2019-03-14 13:22

1a)Does this happen constantly or sometimes is the MMS detected and sometimes is not?

1b) Do the other apps on the same PC or other network devices see the MMS server? Or it is not seen by any device on the network?

1c) I suppose that the line
HTTP GET /, headers: {"host":"192.168.0.250:10222","accept":"text/html, */*","accept-encoding":"deflate, gzip, identity","user-agent":"MediaMonkey5 5.0.0.2165"}
in "MMS do not see MMS even pointed to correct IP and Port.txt" is related to item 2 (i.e. when you entered 192.168.0.250:10222 manually in MM5, right) ??

1d) it seems that auto-discover has failed, but MM5 found Plex server from the QNAP (same IP 192.168.0.250) , but different port.
Could you please run MMS on the same port as Plex to see whether the port is the reason?
- stop Plex server
- start MMS as ./mms --httpPort 32469


2) Yes, this is because you entered link to the web config ( http://192.168.0.250:10222/ ) and not to the device description file ( http://192.168.0.250:10222/description.xml ).
a) I will fix it by specifying custom http header (to be set by MM5) so that MMS knows that it should redirect to device description XML (rather than to the web ui).
b) I will unify the device description XML link with MMW, so that it is rather http://192.168.0.250:10222/DeviceDescription.xml (instead of description.xml)
c) Adding it manually isn't working in MM5 anyway now, because the MMS is not listed under 'Media Servers', but it is listed as device/storage profile under 'Storage & Services' (in order to not be listed twice).
I will need to add the 'Storage & Services' profiles section refresh after manual addition of MMS.

So do not test manual addition now, jest add the feedback re item 1) and assign back to me for fixing 2a-2c)

Ludek

2019-03-14 20:45

developer   ~0052970

Last edited: 2019-03-14 20:47

2a-2c) are fixed in 2166 + newest MMS build

Ludek

2019-03-26 10:20

developer   ~0053103

Could you please do the tests and answer my questions 1a, 1b, 1c, 1d ?