Originally Posted by CharlieU
The reason I mentioned the Port 81 for the web server is that you indicated that you couldn't run the web interface.
Hi Charlie

Thanks for the advice.

I can "see" the QNAP admin pages without any issues...whether it is on port 8080 (as it was) or now on port 81.

OK - so the Sooloos system does not use HTTP/HTTPS protocol to access the QNAP via port 81. So, it must use another port... time to get my "port sniffer" software into operation and see what the C10 is trying to access on the QNAP.

Originally Posted by CharlieU
I can click on the Meridian icon on the QNAP and it brings it up. Looking at the Resource Monitor on the QNAP, I'm showing around 600MB of memory being used for the Sooloos processes and about 1% CPU usage when Sooloos is not being used. The Meridian config app should show all your Sooloos devices. You may have other issues than just with the QNAP.
Interesting - the Sooloos QPKG I have is about 29Mb (prior to expansion/installation). One assumes it must "expand" to something bigger than that, though if it is acting as a "Core" it's internal database would expand depending on the Sooloos system in use.

Of course it could be that the QPKG I have is actually corrupt and/or not complete... and that would explain a lot. Do you have a copy of the QPKG you are using saved somewhere on a PC so you can advise me how big the file is?

Clicking on the M icon only brings up the error as mentioned above... so the Sooloos plugin could be the big issue?

Regards
Tom

Control:10, QNAP TS-251 NAS
Various Hi-Fi Systems (inc: Linn/Quad/Mission/MF/Audio Research)
Former Meridian 101B/105 & MCD then 207/203 Owner