I'll have to investigate this in far more detail (by manually changing the config file back to 9000, then trying the RPC again, or maybe using Wireshark to see where it has actually ended up) but I'd advise holding off setting it to 6000 until I (or anyone else) have looked into this more fully and worked out why it's not happy on that port (if indeed that's the case this is the first time I've tried the current version, so I've absolutely no idea of its idiosyncrasies). I then restarted Twonky, but this time it did not show up on 10.10.10.20:6000 after the restart, nor did it show after disabling and re-enabling the QPKG, so I suspect that Twonky can't work properly on that port (maybe outside the allowable range). Just to be complete, I then tried moving it to from 9001 to 6000 and it 'broke' Twonky (no Twonky config page visible)!!Īs expected, the server returned a page that was mostly blank, other than showing 6000 at the top (so it 'accepted' the proposed change). This was all done on an iPad (on which I'm now typing this response) and it took about 30 seconds and two swigs of red wine to complete. Note that until you restart it, the Twonky config page will still be on the previous port (ie 9000) only after you restart it will it appear on 9001 I then restarted it from the Twonky settings page (under advanced) and I had to then put the below into my browser to find it. In my case, my NAS is on 10.10.10.20 and thus I put the below into a browser's address bar:Īfter hitting enter, you get a mostly blank page returned it just shows the new port (in my case, 9001)

I just installed the QPKG version and tried the RPC method (as that saves faffing about with the config files) on the latest QPKG version (7.0.13) and it worked fine (and I know it works with all previous versions).

Twonky server