Visa 0 Posted August 2, 2018 Posted August 2, 2018 Hi! I recently did a clean install updating from 3.3.0 to 3.5.2, and after initial setup I noticed that I cant install any plugins or browse them. I've tried updating to the latest beta available but that gives the same error, unfortunately. Server dashboard shows the following errors: Check for plugin updates failed, Check for application updates failed info box tells us the following: The SSL connection could not be established, see inner exception. at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.Updates.InstallationManager.GetAvailablePackagesWithoutRegistrationInfo(CancellationToken cancellationToken) at Emby.Server.Implementations.Updates.InstallationManager.GetAvailablePluginUpdates(Version applicationVersion, Boolean withAutoUpdateEnabled, CancellationToken cancellationToken) at Emby.Server.Implementations.ScheduledTasks.PluginUpdateTask.Execute(CancellationToken cancellationToken, IProgress`1 progress) at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options) I've attached the server log. Any help would be appreciated! embyserver.txt
Luke 42077 Posted August 2, 2018 Posted August 2, 2018 Yes it looks like all outgoing https is failing on your machine. This is actually happening due to a defect in the .net core runtime that only occurs when it has trouble reading your local certificate store. A user in this forum found the solution, I will see if i can find that thread. You probably have a certificate in /etc/ssl/certs that the .net core runtime is being denied read access to (If i recall correctly). 1
Solution Visa 0 Posted August 2, 2018 Author Solution Posted August 2, 2018 Yes it looks like all outgoing https is failing on your machine. This is actually happening due to a defect in the .net core runtime that only occurs when it has trouble reading your local certificate store. A user in this forum found the solution, I will see if i can find that thread. You probably have a certificate in /etc/ssl/certs that the .net core runtime is being denied read access to (If i recall correctly). I think I might have found the post you were talking about: https://emby.media/community/index.php?/topic/59531-external-ssl-connections-crashing/page-3&do=findComment&comment=589538 Just like the poster, I had a couple of completely unrelated certificates set to only be readable as root, and that seems to have caused the problem. Thank you so much for helping!
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