Twonky & SqueezeCenter conflict

[kwantai]

Just installed Twonky Media (viewtopic.php?f=47&t=20375) but when I launch the Twonky interface it points to the same address as my SqueezeCenter.

How is that possible and how can I fix this?

[gknippels]

kwantai,

I've ran in to the same problem. Both Twonky and Squeezecenter use port 9000 for communication. However, the fix is easy if you know how to login to your NAS using ssh: simply assign a different port number (I use 9020, but you can select almost any other free availble port) to squeezecenter
You can modify the portnumber that squeezecenter uses by modifying the server settings. These can be found in /var/lib/squeezecenter/prefs/server.prefs
Somewhere deep down in this file is a line that reads:
httpport: 9000

Simply change that to httpport: 9020

Save the file and reboot your NAS. The next time squeezecenter can be accessed through port 9020 and Twonky remains on 9000.

Good luck.
Guido

[kpturner]

I had this problem. At first I found that only SqueezeCenter was listening on port 9000 so I couldn't access Twonky, then after a reboot I found that the reverse had happened and I could access Squeezecenter. When I went to edit the server.prefs file I found that the httpport had been changed to 9001 already ?!

Perhaps the Twonky install did this? Anyway, I can now get to Squeezecenter by manually going to that address on my browser, but the "Setup" button for Squeezecenter on the services page of frontview still points at 9000 (and therefore goes to Twonky).

Sounds like a half baked fixed somewhere in there.

[Briain]

Hi

Easy to fix in a few minutes without SSH: In a web browser, type http://your.nas.ip.address:9000/rpc/stop which stops Twonky. Then you can open the SqueezeCenter setup page in your browser (on 9000) and change the port from 9000 to something like 9050 (from memory, it's under the advance tab then network settings).

Restart the NAS and Twonky will restart (still on 9000) and SC will be on 9050.

Bri

NB You can change the Twonky port via an rpc call too, however, that will likely break the new database rebuild button in Frontview; best just to change SC as described above.

[vallers]

this didn't work for me .. I stopped Twonky, then went back into Squeeze and pressed setup, but got 'cannot display the webpage'

[Briain]

this didn't work for me .. I stopped Twonky, then went back into Squeeze and pressed setup, but got 'cannot display the webpage'

That's odd; I've done it a few times (on several NAS's) and it's always worked fine. I also know of a few Twonky users on the Linn forum who have used this technique to change SC's port, so it should have worked without any problem.

When you say that you 'went back to Squeeze' do you mean that you tried just using your.nas.ip.address:9000 to access the SC user interface (and it opened okay) but then you couldn't access the settings via the hyperlink at the bottom, or do you mean you couldn't access it via the button in Frontview? If you did it the first way, that indicates that SC is running okay, but that for some reason you can't access the setup page. If you tried it the second way and got nowhere, that indicates it might not be running at all, or have a problem with the settings. If you haven't done so already, try the first way (i.e. type the IP:port directly into a browser) and see if it brings up the web interface. If you get nowhere, then try the below trick:

In general, I've found that any issues with SC not responding can always be fixed by uploading the clean db add-on called Clean_SqueezeCenter_DB_1.0.bin (available on the ReadyNAS site). I found that whenever I updated SC, I had to clear the settings before I could open the setup page. I've not had to do that when accidentally forgetting to do it prior to installing Twonky 5 though, but if nothing else works, clearing the SC settings and db should fix it.

NB I have just published a new Twonky tree (click here) which gives the full custom music menu and also now has all the picture and video containers as supplied in the original Twonky tree.

Bri

[vallers]

hi brian, I'm from Linn forum, you've helped me a lot with this (johnv) - I already owe you a few beers!
Both twonky (with your new tree) and squeezecenter are running on the NAS

when I press setup in sqeezecenter I get twonky.

when I stop twonky and press setup on squeezecenter I get nothing

when I look at my squeezebox radio it says it's running squeezecenter HTTP port 9002

if I try to access 9002 directly it can't find it (192.168.0.2:9002)

I have run the clean prog a couple of times as I tried re-installing Squeezecenter

thanks!
John

[Briain]

Hi John

That's most odd. Unfortunately, I can't easily experiment with SC; I don't have in installed any more as I sold my Duet a few months back.

Did you update SC after installing Twonky? If so, I wonder if it detected that 9000 was in use and changed itself to avoid it? I'm at a bit of a loss as to what to suggest next; as I said, when I accidentally installed Twonky without first changing SC, I simply stopped it and then SC could be accessed on 9000 again (and thus changed to something else). It's a bit difficult to figure out exactly what's happening without the experience of it happening to my own NAS's.

If you are really stuck, you could stop Twonky via the tick-box in Frontview, remove SC, run clean db, instal SC again, run clean db again, set up SC as normal, then change the port, then enable Twonky again. It's a bit long winded, but that should really work okay.

Note that you only need change the 9000 port in the SC settings (it has another use for a second port - on 9030, I think - but you can just leave that one as it is).

Bri

[HansAndersHansson]

So I needed to take the long way and clear and deinstall and install. But then it worked. However one minor ptoblem persist. The button in Frontview seem to keep the 9000, so it still lanhes Twonky. So I need to type ip-adress:9001 in the browser to launch squeeze. Any hints?