Emby just stopped working

[techie1298 0]

After running smoothly for I don't know how many years, my Emby docker on Unraid won't start anymore. I presume there was an update last night that is causing this problem. Can anybody point me in the right direction?

Here's the log:

Error Main: Error in appHost.Init
*** Error Report ***
Version: 4.7.0.60
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021
Framework: .NET 6.0.2
OS/Process: x64/x64
Runtime: system/System.Private.CoreLib.dll
Processor count: 8
Data path: /config
Application path: /system
System.ArgumentException: System.ArgumentException: Value does not fall within the expected range.
at Emby.Server.Implementations.Security.AuthenticationRepository.GetDeviceIdFromReportedDeviceId(String reportedDeviceId, String reportedDeviceName, Boolean checkForUpdatedDeviceName, IDatabaseConnection db)
at Emby.Server.Implementations.Security.AuthenticationRepository.Create(AuthenticationInfo info, IDatabaseConnection db, Boolean checkForUpdatedDeviceName)
at Emby.Server.Implementations.Security.AuthenticationRepository.MigrateTokensToTokens2(IDatabaseConnection db)
at Emby.Server.Implementations.Security.AuthenticationRepository.Initialize()
at Emby.Server.Implementations.ApplicationHost.InitDatabases()
at Emby.Server.Implementations.ApplicationHost.Init()
at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken)
Source: Emby.Server.Implementations
TargetSite: Int64 GetDeviceIdFromReportedDeviceId(System.String, System.String, Boolean, SQLitePCL.pretty.IDatabaseConnection)

Info Main: Shutdown complete
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

[Luke 42078]

Hi, yes one other user reported this. We'll have a 4.7.1 maintenance release tomorrow that will resolve this. Thanks.