Brushfyre 1 Posted November 12, 2018 Share Posted November 12, 2018 Minor issue. The plugins catalog will not load and unable to install plugins. It just spins indefinitely. Logs uploaded: sendlogs_brushfyre_synology_rtd1296_ds118_20181112T151954UTC.tgz Thanks! Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 14, 2018 Share Posted November 14, 2018 @@solabc16 what do you think? Link to comment Share on other sites More sharing options...
solabc16 379 Posted November 15, 2018 Share Posted November 15, 2018 Hello @@garvinw73 Just to confirm, this was due to a problem with your network hardware and the issue is now resolved? Best - James Link to comment Share on other sites More sharing options...
Solution Brushfyre 1 Posted November 15, 2018 Author Solution Share Posted November 15, 2018 Resolved. This was actually due to a network hardware issue and was not related to Emby functionality. 1 Link to comment Share on other sites More sharing options...
solabc16 379 Posted November 15, 2018 Share Posted November 15, 2018 Thanks @@garvinw73. Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 3, 2019 Share Posted January 3, 2019 Hi, sorry to bring this up. But I have the same problem and would be interested what the "network hardware problem" was ? thanks, hermann Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 3, 2019 Share Posted January 3, 2019 Btw. I also get the following error: "Check for plugin updates fehlgeschlagen" The operation has timed out.at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsyncInternal>d__18.MoveNext () [0x006b6] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown ---at Emby.Server.Implementations.HttpClientManager.HttpClientManager+<SendAsync>d__15.MoveNext () [0x001f4] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown ---at Emby.Server.Implementations.Updates.InstallationManager+<GetAvailablePackagesWithoutRegistrationInfo>d__48.MoveNext () [0x000c0] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown ---at Emby.Server.Implementations.Updates.InstallationManager+<GetAvailablePluginUpdates>d__57.MoveNext () [0x000a5] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown ---at Emby.Server.Implementations.ScheduledTasks.PluginUpdateTask+<Execute>d__7.MoveNext () [0x000a1] in <8252e50122f84f82af882c36d707f6ce>:0 --- End of stack trace from previous location where exception was thrown ---at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker+<ExecuteInternal>d__68.MoveNext () [0x00156] in <8252e50122f84f82af882c36d707f6ce>:0 Link to comment Share on other sites More sharing options...
Luke 36879 Posted January 3, 2019 Share Posted January 3, 2019 Hi there, can you please attach the complete emby server log? thanks. Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 3, 2019 Share Posted January 3, 2019 Hi Luke, thanks for having a look. Attached the logs. Btw. I have a second, Windows based server which does not show this problem... best, Hermann logs.7z Link to comment Share on other sites More sharing options...
Luke 36879 Posted January 4, 2019 Share Posted January 4, 2019 Are you behind a vpn? do you have synology quick connect enabled? Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 4, 2019 Share Posted January 4, 2019 I am not behind a VPN. QuickConnect is enabled. But to add info: I had EMby already installed on the DS218 in September. And at this time did not experience this problem... Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 4, 2019 Share Posted January 4, 2019 Ok, it seems that a restart of the DS218 fixed this problem. Really sorry for this, but I could not imagine this to be the solution (I restarted Emby Server a few times).. Link to comment Share on other sites More sharing options...
hermann_x5 0 Posted January 4, 2019 Share Posted January 4, 2019 I like to add something that occurs to me could have been the cause for the problem. I have also plex running on this NAS (as both have some advantages and disadvantages and I am still not sure which way to finally go) and Plex had troubles with Metadata. I read in a forum that maybe this had something todo with IP v6. So. I deactivated IP v6 in DSM yesterday - which did not help. But today, after restarting the diskstation, Plex worked fine and Emby also did not suffer from this problem anymore. So, most likely, it's a long shot, but maybe these kinds of problems have something todo with IPv6... Link to comment Share on other sites More sharing options...
Schaekel 0 Posted January 4, 2019 Share Posted January 4, 2019 This seems to occure after a software update (DSM). I also had to restart my NAS in order to have connections (plugin-checks, scrapping and so on) via emby. Link to comment Share on other sites More sharing options...
Luke 36879 Posted January 4, 2019 Share Posted January 4, 2019 Thanks for the feedback. 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