Sign in   |  Join   |  Help

Moment User? Twonky Server has been removed from QNAP OS v4.3.x

rated by 0 users
Not Answered This post has 0 verified answers | 68 Replies | 3 Followers

kimhav
Top 500 Contributor
Malmo, Sweden
240 Posts
OFFLINE
Gold Member
kimhav posted on Wed, Jan 4 2017 11:00 AM

If You are making use of Twonky Server from the QNAP App Center on their NAS then beware of that they have dropped the support for Twonky Server in the current beta v4.3.x and moving forward. Quoting a brief response that I got from the QNAP support after that I realized that Twonky isn't no longer combatible with the current beta:

"After 4.3.x, Twonky service is not available on NAS system. For DLNA service, we will suggest please apply the built-in DLNA service and install media streaming add-on app on App center for advanced management too."

Depending on what QNAP NAS you have, you can quickly overcome this issue by making use of the ContainerStation and run a dedicated Twonky Server to support the BeoSound Moment. The container solution dosn't add any significant overhead compared using the twonky server from the app center.

All Replies

Sal
Top 75 Contributor
California, USA
1,197 Posts
OFFLINE
Bronze Member
Sal replied on Sun, Jan 8 2017 5:18 PM

Short update:

QNAP TS 451+ using QTS 4.2.2. Have an A6 and an Essence which I use via the BeoMusic app.

MinimServer installed and run: BeoMusic app can't see it under A6 and Essence.

Successfully installed Twonky in a container as instructed including a symlink to my Music folder. The settings show that Twonky has indexed the files and all is good. BeoMusic can't see it under both of my products. (is ContainerStation sandboxed in any way that it runs on it's own network stack? If so, how to I make it accessible outside of it's container?)

Restarted my NAS AND checked all my settings and the only servers that show in my products list is Plex and Twonky run from the main QTS screen (not The container). QNAP DLNA still doesn't show.

 

Ugh.

mbolo01
Top 75 Contributor
Annecy - France
1,716 Posts
OFFLINE
Gold Member

Sal:
BeoMusic can't see it under both of my products.

Sal: did you set the Network in Bridge mode when creating your Container?

 

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

Sal
Top 75 Contributor
California, USA
1,197 Posts
OFFLINE
Bronze Member
Sal replied on Sun, Jan 8 2017 5:58 PM

So the first time, I didn't. I deleted everything and started over the second time I did, and now beoMusic can see the newly created Twonky Server in the source list, but I have nothing shared. Unfortunately, the URL for the Twonky Settings page which showed in Container Settings the first time I set it up is blank, so there's no way for me to get to the Twonky settings to set up the shared folder. I can't seem to find a way to access TwonkyServer's maintenance / settings web URL GUI.

 

mbolo01
Top 75 Contributor
Annecy - France
1,716 Posts
OFFLINE
Gold Member

Sal:
I can't seem to find a way to access TwonkyServer's maintenance / settings web URL GUI.

If you chose DHCP in the network settings and if you have a mean to identify which IP was provided to the Container, then you can connect to the Twonky server using http://IP address:9000

I recommend you set a fixed IP address out of your DHCP range, which means rebuild a Container again .....

You are almost there Sal!!!

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

Sal
Top 75 Contributor
California, USA
1,197 Posts
OFFLINE
Bronze Member
Sal replied on Sun, Jan 8 2017 6:27 PM

mbolo01:
I recommend you set a fixed IP address out of your DHCP range

 

I think I need a tutorial on which static IP addresses to use. My QNAP has one which I know. The dialog box shows 4 places to enter different IP addresses. I can find out the IP addresses or the other devices on my network as well. Do I just pick one that isn't used? What is the range?

kimhav
Top 500 Contributor
Malmo, Sweden
240 Posts
OFFLINE
Gold Member

Sal:
I think I need a tutorial on which static IP addresses to use. My QNAP has one which I know. The dialog box shows 4 places to enter different IP addresses. I can find out the IP addresses or the other devices on my network as well. Do I just pick one that isn't used? What is the range?

If You're unsure which IP being used on your internal network you could use an IP scanner to check what you have internally of devices and what IP addresses is being used. This often gives you an indicates of where the DHCP range start as the dhcp based clients usually are within a pre-defined range and looks like they're in a cluster.

 

 

Carolpa
Top 75 Contributor
1,104 Posts
OFFLINE
Bronze Member
mbolo01:

I tried with 8Player lite and (1) the QNAP DLNA Server source can be played on the iPhone (2) Only the BS Moment appears in the list of possible players, not the A6 (3) When the Moment is selected, the processing wheel keeps turning, the application is stuck, no sound out of the Moment.

Fyi: I can stream from the Twonky server UI to the BS Moment without issue

the 8player does have the same behavior as BeoMusic. So it is not a BeoMusic issue!

BeoMusic does work with several other DLNA servers as controller between the server and the players Bs35, A6, etc. But not with the QNAP media server

2 options:

different incompatible DLNA standard versions

or QNAP issue

Carolpa
Top 75 Contributor
1,104 Posts
OFFLINE
Bronze Member
kimhav:

Same here, the QNAP sees the Beosound Moment but not the other way around; did try to make use of both the standard port 8200 which QNAP makes use of for it's media server and as well port 9000 if the Moment excepts to see a Twonky server which didn't make any difference.

Twonky works through port 9000

But to control Twonky with a controller like 8 player port 9100 is used
kimhav
Top 500 Contributor
Malmo, Sweden
240 Posts
OFFLINE
Gold Member

Sal:
The dialog box shows 4 places to enter different IP addresses. I can find out the IP addresses or the other devices on my network as well.

Hmm seems that some of responses has to be moderated and guess it's due to external links in them. So here is another response which was supposed to be included in the first one. But, here is how it could look like if you fill in the IP in the Container Network configuration and based on that you for example used the Advanced IP Scanner to figure out an "free" IP:

 

kimhav
Top 500 Contributor
Malmo, Sweden
240 Posts
OFFLINE
Gold Member

Carolpa:
Twonky works through port 9000

But to control Twonky with a controller like 8 player port 9100 is used

Yeah, aware about that Twonky uses port 9000 but if we're trying to get QNAP own media server to run and it's runs on port 8200 I would assume that the Moment wouldn't find it as it might only look for port 9000, or? In that case the QNAP MS would have to be changed from port 8200 to 9000.

 

 

mbolo01
Top 75 Contributor
Annecy - France
1,716 Posts
OFFLINE
Gold Member

kimhav:
the Moment wouldn't find it as it might only look for port 9000

9000 is not a default port for DLNA Services but for Twonky server management, the DLNA servers are advertising their service through SSDP and DLNA Players are then building a directory of available DLNA servers.

I'm not sure about what makes the QNAP DLNA Server invisible to some B&O devices, but there is definitively an issue between these two brands.

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

Sal
Top 75 Contributor
California, USA
1,197 Posts
OFFLINE
Bronze Member
Sal replied on Sun, Jan 8 2017 11:21 PM

Thanks to mbolo01's help, I've got everything sorted -- except for, of course, the reason why QNAP's own DLNA doesn't show on BeoMusic. That being said, since I'm still running QTS 4.2.2, Twonky from the App Center works, and if I choose, for some inexplicable reason, to their next OS, I have set up, and know how to set up a Twonky Server within Container Center.

Once again! This community of users is great!

MircoHH
Top 500 Contributor
Germany
259 Posts
OFFLINE
Silver Member

Okay, same container image (dlaventu/twonkyserver) as I used then but what made the difference to get the Moment to find the twonky server was to make use of Bridge Mode for the network. 

 

 

How Do you switch it to BRIDGE MODE?

mbolo01
Top 75 Contributor
Annecy - France
1,716 Posts
OFFLINE
Gold Member

MircoHH:
How Do you switch it to BRIDGE MODE?

At creation time only, look at the setup screen upper in this thread.

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

mbolo01
Top 75 Contributor
Annecy - France
1,716 Posts
OFFLINE
Gold Member
UPDATE: the Container setup introduced an issue impacting my Moment.

I'm curious to know if other QNAP users having a Twonky server running in a Docker Container do have the issue too:

After a QNAP restart, followed by a Moment restart, the Moment displays a DLNA server unavailable error message. (I can provide more details if needed) To temporarily recover, the Twonky server has to be selected again in the DLNA source, but it triggers a full scan and is valid until the next restarts.

To get rid of the issue completely, remove the Container station app, restart the QNAP, install the Twonky QNAP package found on the Twonky download site (not the EOM package found in App Center)

You'll need an activation key, same than the one use for the Docker Twonky server

BS Moment, BS Core, BG 4002, BC 4500, BS1, BL18, BL19, BL8000 + RCV1, A6, M5, M3, A1, P6 (tks Botty), H5, TR1

Page 4 of 5 (69 items) < Previous 1 2 3 4 5 Next > | RSS
Beoworld Security Certificate

SSL