Serverhome.it 0 Posted November 6, 2024 Posted November 6, 2024 I entered the emby key on true nas but it says it is invalid or missing, doing a search I was told that the emby server is unable to connect to the internet and therefore was unable to register the key, can you help me?
ebr 16184 Posted November 7, 2024 Posted November 7, 2024 Hi. Your server needs to be able to reach ours over the internet to validate. This may mean you need to configure a firewall or other network settings to allow this. Have you done that? 1
Serverhome.it 0 Posted November 7, 2024 Author Posted November 7, 2024 the server downloads updates periodically from the internet so I don't think it won't be able to come out, then the emby server can be reached from the outside with a smartphone app and this was possible by opening the necessary ports on the router, I've been banging for days but I can't get to it at the head
ebr 16184 Posted November 7, 2024 Posted November 7, 2024 Please attach the server log from when you try to save the key.
Neminem 1519 Posted November 7, 2024 Posted November 7, 2024 Quote 2024-11-07 05:57:10.530 Error SecurityManager: Error checking registration status of MBSupporter *** Error Report *** Version: 4.8.10.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.1.74-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 Framework: .NET 6.0.31 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 2 Data path: /config Application path: /system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://mb3admin.com/admin/service/registration/validate timed out ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. ---> System.TimeoutException: A task was canceled. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) --- 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.Security.PluginSecurityManager.UpdateRegistrationStatus(String feature, String key, String version, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. Source: System.Net.Http TargetSite: Void HandleFailure(System.Exception, Boolean, System.Net.Http.HttpResponseMessage, System.Threading.CancellationTokenSource, System.Threading.CancellationToken, System.Threading.CancellationTokenSource) at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) InnerException: System.TimeoutException: A task was canceled. Source: TargetSite: InnerException: System.Threading.Tasks.TaskCanceledException: A task was canceled. Source: System.Private.CoreLib TargetSite: Void ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) You have something blocking access to https://mb3admin.com. Try removing IPv6 Restart emby and try again.
pwhodges 2012 Posted November 7, 2024 Posted November 7, 2024 (edited) 56 minutes ago, Neminem said: Try removing IPv6 My heart sinks every time I see this. My home network has had IPv6 for ten years now, and it has never once had an issue caused by it. Paul Edited November 7, 2024 by pwhodges
Neminem 1519 Posted November 7, 2024 Posted November 7, 2024 1 minute ago, pwhodges said: My heart sinks every time I see this. My home network has had IPv6 for ten years now, and it has never once caused an issue caused by it. True, but seen to many issues with it, to not try without
Serverhome.it 0 Posted November 7, 2024 Author Posted November 7, 2024 I tried to delete the string on ipv6 and directly restarted the NAS but nothing
Luke 42079 Posted November 7, 2024 Posted November 7, 2024 2 hours ago, Serverhome.it said: I tried to delete the string on ipv6 and directly restarted the NAS but nothing What exactly did you do? What does it look like now?
Serverhome.it 0 Posted November 8, 2024 Author Posted November 8, 2024 I deleted ipv6 as suggested, but when I restart the NAS it puts it back
Serverhome.it 0 Posted November 8, 2024 Author Posted November 8, 2024 (edited) Edited November 8, 2024 by Serverhome.it
ebr 16184 Posted November 8, 2024 Posted November 8, 2024 Hi. What he was suggesting was disabling IPv6 support on the network adapter. I also don't know that this will have any impact but I guess it is worth a shot.
296926581 0 Posted November 10, 2024 Posted November 10, 2024 Disabled IPV6, the same problem, I use in China, could it be the firewall problem
Serverhome.it 0 Posted November 11, 2024 Author Posted November 11, 2024 I gave up, I tried them all, I'm just sorry I wasted money on the subscription
296926581 0 Posted November 11, 2024 Posted November 11, 2024 I have two lines of network operators here, one line can be authenticated, the other line can not be authenticated, I think the network operator's firewall organized the license authentication, the use of VPN authentication can be successful.
rbjtech 5284 Posted November 11, 2024 Posted November 11, 2024 @Neminemhas already given the reason earlier in the thread. https://mb3admin.com/admin/service/registration/validate By simply running the above http request in your browser with the same network/access as the emby server - does it come back with something like {"featId":"","registered":false,"expDate":"1900-01-01","key":null} or no response. If no response, then that is why it is not working and is caused by your local network/setup, emby is not at fault here.
rbjtech 5284 Posted November 11, 2024 Posted November 11, 2024 14 minutes ago, Serverhome.it said: ok - and you have done this from the trunas server ? there is no point in doing that on your own desktop browser as that is not where the access request is coming from. you may need to use a command line utility from the tru nas admin console - maybe curl or something like that. (if it has a browser, then great - I'm not familiar with the tru nas OS)
ebr 16184 Posted November 11, 2024 Posted November 11, 2024 51 minutes ago, Serverhome.it said: I can see your key has not successfully validated so something is blocking. The browser test can only tell you if something outside your network is blocking. Firewall rules are process-specific so it is likely your firewall blocking the server process.
Luke 42079 Posted November 17, 2024 Posted November 17, 2024 On 11/12/2024 at 4:32 AM, 296926581 said: 我无法登录,应该是网络运营商的防火墙被封了,现在我该怎么办 HI, what about using a VPN?
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