I went in with WinSCP and found and deletetd the .ini in the ...etc/... folder.
Now it's working again. great. thank you.
ps | grep twonky6624 admin 412 S /mnt/HDA_ROOT/twonkymedia/twonkymedia -inifile /etc/config/twonkyvision-mediaserver6.ini ...
8123 admin 4880 S /mnt/HDA_ROOT/twonkymedia/twonkymediaserver -inifile /etc/config/twonkyvision-mediaserver6.ini ...
19345 admin 568 S grep twonky
[~] #
enableweb=frank_t wrote:Hi,
I had the same problem on my TS-219P II.
My first advice is: don't edit/delete any file before you know which is the right one!
Here is how I fixed the problem under Windows:
1. Log-in on your NAS as admin via ssh (I used putty) to be able to execute some commands.
2. Open a SFTP connection to your NAS (I used WinSCP) in parallel to edit/delete files.
3. Determine which .ini file the Twonky Media Server uses:
typein the ssh command line.
- Code: Select all
ps | grep twonky
(The command ps gets a list of all active processes on the NAS and grep filters out all lines containing the text "twonky".)
4. Above command gives you something like this:
6624 admin 412 S /mnt/HDA_ROOT/twonkymedia/twonkymedia -inifile /etc/config/twonkyvision-mediaserver6.ini ...
8123 admin 4880 S /mnt/HDA_ROOT/twonkymedia/twonkymediaserver -inifile /etc/config/twonkyvision-mediaserver6.ini ...
19345 admin 568 S grep twonky
[~] #
As you can see, Twonky is using the .ini file /etc/config/twonkyvision-mediaserver6.ini.
(Make sure that the putty's window is wide enough, so that you can see the hole path of the .ini file.)
5. With WinSCP, navigate to folder /etc/config and double-click the file twonkyvision-mediaserver6.ini to edit it.
6. In the editor, search forand set its value to 2.
- Code: Select all
enableweb=
7. Save the file and restart the UPnP service.
Users browsing this forum: No registered users and 1 guest