pr3dict 31 Posted March 2, 2018 Share Posted March 2, 2018 haha I have a problem... I did apt-get remove emby-server and then I downlaoded the file and tried to unpack... What I do wrong. Link to comment Share on other sites More sharing options...
Luke 29064 Posted March 2, 2018 Share Posted March 2, 2018 is your system user named emby? Link to comment Share on other sites More sharing options...
pr3dict 31 Posted March 2, 2018 Share Posted March 2, 2018 I have a user named emby so when it creates files it has the same permissions as emby so emby can do its thing and not have a permission problem. Link to comment Share on other sites More sharing options...
DarWun 125 Posted March 2, 2018 Author Share Posted March 2, 2018 (edited) Ok so you are running our OBS based packages, and that is indeed our legacy installation package. You can continue to use this for as long as you like. This edition does not auto-update either so your update process is just the typical apt-get update linux command. We are no longer doing any new development on these packages (but we will post new server versions) so you would just have to ignore the error, which really shouldn't bother you because as I previously mentioned, it is only used to display if an update is available. it's not actually used for updating. If you would like to switch to our newer installation package, there are numerous benefits: this error goes away, faster performance, more stable, self-contained dependencies, which means no more mono, etc. However, this would require you uninstall your current package, and then install the new package fresh: https://emby.media/download Just so I am clear, is this applicable to the Synology NAS installation packages as well? I'm not familiar with the term "OBS based packages". So maybe that is the clue that it isn't applicable. But just to be safe I figured I'd ask. I haven't seen anything about a newer installation package that should be used for updating Emby on Synology. Edited March 2, 2018 by DarWun Link to comment Share on other sites More sharing options...
Luke 29064 Posted March 2, 2018 Share Posted March 2, 2018 Just so I am clear, is this applicable to the Synology NAS installation packages as well? I'm not familiar with the term "OBS based packages". So maybe that is the clue that it isn't applicable. But just to be safe I figured I'd ask. I haven't seen anything about a newer installation package that should be used for updating Emby on Synology. No, you can ignore everything i said there. He's piggybacking his Debian question into a Synology thread, and that's usually what ends up happening 1 Link to comment Share on other sites More sharing options...
DarWun 125 Posted March 3, 2018 Author Share Posted March 3, 2018 Great, thanks ! I logged in to root on my Synology NAS using PuTTY. I typed "export MONO_TLS_PROVIDER=btls" on the command line and hit enter. There was no error given. But there was also no feedback of any kind given to indicate that anything had happened. I wasn't sure if a reboot of the NAS was necessary. But I did so just in case. After the server restarted, Emby still throws up a "SecureChannelFailure" error when checking for server updates. As others have mentioned, this isn't a big deal as notifications and delivery of updates for the Synology version of Emby come through the NAS package center. So as long as it doesn't affect delivery of plug-in updates from github (which so far it doesn't seem to), all is good. Link to comment Share on other sites More sharing options...
Luke 29064 Posted March 3, 2018 Share Posted March 3, 2018 Thanks for the info. Link to comment Share on other sites More sharing options...
mutu310 70 Posted March 5, 2018 Share Posted March 5, 2018 For all it's worth, I have the same problem on my DS213j. Link to comment Share on other sites More sharing options...
mutu310 70 Posted March 5, 2018 Share Posted March 5, 2018 By the way, https://synology.emby.media seems down (?) Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 6, 2018 Share Posted March 6, 2018 Hello All For the Synology/XPEnology users (to avoid confusion) who are seeing this error reported in the logs, can you let me know which country you're in - either here or via PM, if you'd prefer not to post that publicly. It may be CDN related and hence why it's not happening universally; if it was a limitation of the released binaries, we would expect this to fail consistently across all platforms/locations. With the latest releases there really shouldn't be any problem with GitHub's switch to accepting TLS v1.2 only. Best - James Link to comment Share on other sites More sharing options...
DarWun 125 Posted March 7, 2018 Author Share Posted March 7, 2018 Hello All For the Synology/XPEnology users (to avoid confusion) who are seeing this error reported in the logs, can you let me know which country you're in - either here or via PM, if you'd prefer not to post that publicly. It may be CDN related and hence why it's not happening universally; if it was a limitation of the released binaries, we would expect this to fail consistently across all platforms/locations. With the latest releases there really shouldn't be any problem with GitHub's switch to accepting TLS v1.2 only. Best - James Canada home base here. Link to comment Share on other sites More sharing options...
mutu310 70 Posted March 7, 2018 Share Posted March 7, 2018 Hello All For the Synology/XPEnology users (to avoid confusion) who are seeing this error reported in the logs, can you let me know which country you're in - either here or via PM, if you'd prefer not to post that publicly. It may be CDN related and hence why it's not happening universally; if it was a limitation of the released binaries, we would expect this to fail consistently across all platforms/locations. With the latest releases there really shouldn't be any problem with GitHub's switch to accepting TLS v1.2 only. Best - James Malta. Link to comment Share on other sites More sharing options...
Darkjeje 11 Posted March 7, 2018 Share Posted March 7, 2018 (edited) Hello James, When I want to install the update in my DSM, I click to download, but when the installation begin, I have a message which indicate more or less "This package have no autorisation for installation". If I choose "trust level" to any publisher, the installation is OK, but not when I choose trusted publishers,... I am in France. Thank you for helping Edited March 7, 2018 by Darkjeje Link to comment Share on other sites More sharing options...
Glyde62 46 Posted March 18, 2018 Share Posted March 18, 2018 I am also getting this error Error: SecureChannelFailure (The authentication or decryption has failed.) No solution yet? Link to comment Share on other sites More sharing options...
Luke 29064 Posted March 18, 2018 Share Posted March 18, 2018 Not yet but it will not affect any core features. Link to comment Share on other sites More sharing options...
Glyde62 46 Posted March 19, 2018 Share Posted March 19, 2018 Not yet but it will not affect any core features. yeah everything seems to be working as usual Just don't like seeing errors Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 19, 2018 Share Posted March 19, 2018 Hello @@Glyde62 What Synology hardware platform are you running on and what version of DSM? Anybody else who is experiencing this issue, please can you post the same. Best - James Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 19, 2018 Share Posted March 19, 2018 (edited) Hello James, When I want to install the update in my DSM, I click to download, but when the installation begin, I have a message which indicate more or less "This package have no autorisation for installation". If I choose "trust level" to any publisher, the installation is OK, but not when I choose trusted publishers,... I am in France. Thank you for helping Hello @@Darkjeje This is a different issue to the "Error: SecureChannelFailure When Checking for Application Updates", which we have seen on a handful of systems. Typically it seems to occur because the certificate has 'disappeared' from Package Center - we don't know at the moment what causes this. Have a look at... https://emby.media/community/index.php?/topic/53177-cant-update-package-from-unknown-published/?p=514213 ...and... https://emby.media/community/index.php?/topic/53177-cant-update-package-from-unknown-published/?p=516065 Best - James Edited March 19, 2018 by solabc16 Link to comment Share on other sites More sharing options...
kesm 22 Posted March 19, 2018 Share Posted March 19, 2018 Hello @@Glyde62 What Synology hardware platform are you running on and what version of DSM? Anybody else who is experiencing this issue, please can you post the same. Best - James Hi, I have this issue on a DS414 with DSM 6.1.5-15254 Update 1, available if you need more information. Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 19, 2018 Share Posted March 19, 2018 Thanks @@kesm. @@DarWun, @@mutu310 and @@Glyde62 - if you could confirm what Synology hardware platform are you running on and DSM version as well, that would be helpful. Best - James Link to comment Share on other sites More sharing options...
DarWun 125 Posted March 19, 2018 Author Share Posted March 19, 2018 (edited) Thanks @@kesm. @@DarWun, @@mutu310 and @@Glyde62 - if you could confirm what Synology hardware platform are you running on and DSM version as well, that would be helpful. Best - James @@solabc16 My setup is the same as @@kesm 's...Emby on a DS414 NAS with DSM 6.1.5-15254 Update 1. The DS414 has a Marvell Armada XP MV78230 dual core processor (i.e. Armadaxp package architecture). Let me know if you require any further information. Cheers, DarWun Edited March 19, 2018 by DarWun Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 20, 2018 Share Posted March 20, 2018 (edited) Hello All We've got to the bottom of this now and are working on a solution to resolve this error, with the hope of including it in the next stable release. As Luke mentioned above https://emby.media/community/index.php?/topic/56391-error-securechannelfailure-when-checking-for-application-updates/?p=557639, this issue does not affect any core features. I'll post further updates in due course and may ask for volunteers to assist with testing the fix. Best - James Edited March 20, 2018 by solabc16 1 Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 22, 2018 Share Posted March 22, 2018 Hello All A quick update, internal testing has been positive so far and we now have a package available for 'armadaxp' based systems, starting with release 3.3.1.6-beta. If you are experiencing this issue and are currently signed-up to the beta channel, let me know so I can make the updated package available for you to test. Best - James 1 Link to comment Share on other sites More sharing options...
kesm 22 Posted March 22, 2018 Share Posted March 22, 2018 Hello All A quick update, internal testing has been positive so far and we now have a package available for 'armadaxp' based systems, starting with release 3.3.1.6-beta. If you are experiencing this issue and are currently signed-up to the beta channel, let me know so I can make the updated package available for you to test. Best - James That's my case, I'm available for testing Link to comment Share on other sites More sharing options...
solabc16 379 Posted March 22, 2018 Share Posted March 22, 2018 Hello @@kesm If you refresh Package Center now, you should find 3.3.1.6-beta available. Let us know how you get on... Best - James Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now