Jump to content

Can't Get Metadata/Identify/Re-activate Premiere


eepeeseejay

Recommended Posts

eepeeseejay

---- Recently downloaded media failed to automatically update
---- When identifying manually, I get 'no results' 
---- Organize Files plugin failed to move any files

+I was not ready to play w/SQL, so I went for library.db delete/rebuild.
+No improvement, so I opted to uninstall & re-install.
+Added one movie file to a Library folder.
---- same identification trouble.
---- now, re-entering premiere key generates 'Thank You' but then shows "Emby Premiere key is missing or Invalid"

I think permissions are good, but also I don't think they're the problem.
+Set as Windows Service using guide form Knowlege Base, JIC

Based on logs, looks like it's probably network-related.
+Verified Windows Firewall is set to allow Emby Server.
+Restarted Computer, Modem, Router, Computer again.

nothing I have tried has worked. I am out of ideas.
I checked the log, but all I can see is a whole bunch of:
 

Quote
2023-03-11 20:12:40.859 Error App: Error getting connection info
*** Error Report ***
Version: 4.8.0.21
Command line: C:\Users\E\AppData\Roaming\Emby-Server\system\EmbyServer.dll
Operating system: Microsoft Windows 10.0.22621
Framework: .NET 6.0.10
OS/Process: x64/x64
Runtime: C:/Users/E/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
Processor count: 2
Data path: C:\Users\E\AppData\Roaming\Emby-Server\programdata
Application path: C:\Users\E\AppData\Roaming\Emby-Server\system
System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: The requested address is not valid in its context. (connect.emby.media:443)
---> System.Net.Sockets.SocketException (10049): The requested address is not valid in its context.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
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.Networking.RemoteAddressEntryPoint.GetIpAddress(String lookupUrl)
at Emby.Server.Implementations.Networking.RemoteAddressEntryPoint.TimerCallback(Object state)
Source: Emby.Server.Implementations
TargetSite: Void MoveNext()
InnerException: System.Net.Sockets.SocketException: The requested address is not valid in its context.
Source: System.Net.Sockets
TargetSite: Void ThrowException(System.Net.Sockets.SocketError, System.Threading.CancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)

 

embyserver-1.txt

Link to comment
Share on other sites

Hello eepeeseejay,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:


Thank you.

Emby Team

Link to comment
Share on other sites

HI, yes, all outgoing requests are failing. Typical causes of this are firewall, security software, or VPN. Can you look into those? 

Another thing to try would be disabling ipv6 in your router. Please let us know if this helps. Thanks.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...