Twonky 8.5 released
- twonky-christian
- Lynx Technology Staff
- Posts:1123
- Joined:Fri Sep 10, 2004 3:16 pm
- AV Hardware:PC
- Location:Berlin
- Contact:
Hi,
we now released Twonky 8.5
http://twonkyforum.com/downloads/8.5/
Features:
- nicer web UI on tablets like fullscreen video and slideshows
- now you can just go to http://twonkyserver.twonky.com to access your local Twonky Server web UI (redirect)
thanks
Christian
we now released Twonky 8.5
http://twonkyforum.com/downloads/8.5/
Features:
- nicer web UI on tablets like fullscreen video and slideshows
- now you can just go to http://twonkyserver.twonky.com to access your local Twonky Server web UI (redirect)
thanks
Christian
Re: Twonky 8.5 released
Thanks for the update, though the URL "twonkyserver.twonky.com" does not work on my QNAP TVS-463 running QTS 4.3.4twonky-christian wrote:Hi,
- now you can just go to http://twonkyserver.twonky.com to access your local Twonky Server web UI (redirect)
thanks
Christian
Re: Twonky 8.5 released
The http://twonkyserver.twonky.com does not work for me either ![Sad :-(](./images/smilies/icon_sad.gif)
I would like to add the .ini option to have "music/format" in advanced navigation tree, but i cannot find the syntax, can you help please?
Cheers
![Sad :-(](./images/smilies/icon_sad.gif)
I would like to add the .ini option to have "music/format" in advanced navigation tree, but i cannot find the syntax, can you help please?
Cheers
Re: Twonky 8.5 released
I have a question regarding the need to log in to start the server....
I can understand that in initial login may be needed when setting up the server, and I can understand the use of a remote server to validate the use of the registration key. However, it seems that the user is also required to log in with a username and password every time that the server or NAS hardware on which TwonkyServer is installed is rebooted, for example after a power failure. Is this intended?
I expected that the login would somehow be saved so that restarts would be fairly painless. The problem is that if the server or NAS has to be restarted for any reason, then someone must login via a browser before they can access the content that TwonkyServer is there to provide. That's almost OK if I am around, but I cannot rely on other family members to do this in my absence, when all they want to do is to switch on the hifi or play something on a smart radio.
I'd appreciate some feedback on this. Have I missed something that says "save settings" or similar? Thanks.
I can understand that in initial login may be needed when setting up the server, and I can understand the use of a remote server to validate the use of the registration key. However, it seems that the user is also required to log in with a username and password every time that the server or NAS hardware on which TwonkyServer is installed is rebooted, for example after a power failure. Is this intended?
I expected that the login would somehow be saved so that restarts would be fairly painless. The problem is that if the server or NAS has to be restarted for any reason, then someone must login via a browser before they can access the content that TwonkyServer is there to provide. That's almost OK if I am around, but I cannot rely on other family members to do this in my absence, when all they want to do is to switch on the hifi or play something on a smart radio.
I'd appreciate some feedback on this. Have I missed something that says "save settings" or similar? Thanks.
-
- Posts:3
- Joined:Tue Dec 19, 2017 7:08 pm
- AV Hardware:Onkyo TX-NR656 AVR
Raspberry Pi 2B
NetGear ReadyNAS NV+ v2 NAS using NTP - Location:San Diego
Re: Twonky 8.5 released
Christian,
I have the same request as S80_UK: Can you fix Twonky Server to not require a login after the host server reboots?
I have Twonky Server running on a Raspberry Pi, and I sometimes need to reboot it, or power if off. Upon power-up, although Twonky Server is being run as a service on the Raspbian OS, a web login to the Twonky Admin account is required before my smart phones or the Onkyo AVR can access the music files.
Thank you for considering this request.
Greg in San Diego.
I have the same request as S80_UK: Can you fix Twonky Server to not require a login after the host server reboots?
I have Twonky Server running on a Raspberry Pi, and I sometimes need to reboot it, or power if off. Upon power-up, although Twonky Server is being run as a service on the Raspbian OS, a web login to the Twonky Admin account is required before my smart phones or the Onkyo AVR can access the music files.
Thank you for considering this request.
Greg in San Diego.
Re: Twonky 8.5 released
Hi Greg,GregBinSD wrote:Christian,
I have the same request as S80_UK: Can you fix Twonky Server to not require a login after the host server reboots?
I have Twonky Server running on a Raspberry Pi, and I sometimes need to reboot it, or power if off. Upon power-up, although Twonky Server is being run as a service on the Raspbian OS, a web login to the Twonky Admin account is required before my smart phones or the Onkyo AVR can access the music files.
Thank you for considering this request.
Greg in San Diego.
I am not sure if this will help you, but I think I have a solution. After logging in via the web page, a new folder is created: /var/lynxtechnology and that folder contains a file called token
In my server (I use unRAID on a PC platform) that folder is held in a RAM based filing sytem and is lost at power off. So while the server is up and running I manually copy the folder to some non-volatile storage. In my case that's a USB stck, but it could be on an SD card perhaps in your case. I also modify my boot up script to copy that folder back from storage to the /var folder with something like this...
Code: Select all
cp -r /boot/config/lynxtechnology /var/
This restore of the folder and token file must be executed before running the startup script for twonkyserver.
In my case /boot/config is just a handy place - I am not a Pi user, but it's likely you can find somewhere similar.
The result of this is that I can now power down my server and restart later with twonkyserver starting up correctly and not requiring a subsequent login. Whether this works long term I don't know, but I thought it was worth sharing.
Hope this helps you.
Cheers,
Les.
(S80_UK)
-
- Posts:3
- Joined:Tue Dec 19, 2017 7:08 pm
- AV Hardware:Onkyo TX-NR656 AVR
Raspberry Pi 2B
NetGear ReadyNAS NV+ v2 NAS using NTP - Location:San Diego
Re: Twonky 8.5 released
Les,
Thank you for sending me your solution to the issue of requiring a Twonky administrator to login before Twonky Server will allow clients to connect. It works perfectly for me on the RPi. Following your logic:
I copied the current /var/lynxtechnology directory and its contents to the /boot directory, a safe place to store it.
Then, I added the same line, which you did, near the bottom of the /boot/config.txt file. In addition, I added some comments so that I would remember why I did this!
# Copy Twonky Server token from saved location to the Twonky var location.
# This is a kludge suggested by Les (S80_UK) on the Twonky Server forum.
# If this token does not already exist when Twonky Server is started, then
# a manual login by the Twonky admin is required before clients can connect
# to Twonky. This eliminates that need.
cp -r /boot/lynxtechnology /var/
Thanks again for sharing your solution to this issue.
Greg
Thank you for sending me your solution to the issue of requiring a Twonky administrator to login before Twonky Server will allow clients to connect. It works perfectly for me on the RPi. Following your logic:
I copied the current /var/lynxtechnology directory and its contents to the /boot directory, a safe place to store it.
Then, I added the same line, which you did, near the bottom of the /boot/config.txt file. In addition, I added some comments so that I would remember why I did this!
# Copy Twonky Server token from saved location to the Twonky var location.
# This is a kludge suggested by Les (S80_UK) on the Twonky Server forum.
# If this token does not already exist when Twonky Server is started, then
# a manual login by the Twonky admin is required before clients can connect
# to Twonky. This eliminates that need.
cp -r /boot/lynxtechnology /var/
Thanks again for sharing your solution to this issue.
Greg
Re: Twonky 8.5 released
Greg,
You're very welcome. I am glad that the solution worked for you as well. Thanks for letting me know. Your feedback may help others in the future. Perhaps reasonably, the expected use for the Linux based builds is on a hard-disk based system, where the token would not disappear as soon as power is removed.
It's just a shame that the forums are no longer actively supported by Lynx Technology / Twonky. They seem to be more of a business-to-business organisation these days, relying on their licensees to support end users.
All the best,
Les.
You're very welcome. I am glad that the solution worked for you as well. Thanks for letting me know. Your feedback may help others in the future. Perhaps reasonably, the expected use for the Linux based builds is on a hard-disk based system, where the token would not disappear as soon as power is removed.
It's just a shame that the forums are no longer actively supported by Lynx Technology / Twonky. They seem to be more of a business-to-business organisation these days, relying on their licensees to support end users.
All the best,
Les.
Re: Twonky 8.5 released
Thanks for the update!!!
-
- Posts:1
- Joined:Fri Nov 15, 2019 11:49 am
- AV Hardware:UPnP servers
- Contact: