Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

New Emby Docker

Featured Replies

6 hours ago, Blaqwolf said:

If there is a dev reading, can we get the option to get missing episodes back into the list so we KNOW we are missing something?

Definitely one for the Emby developers over on their forum if you don't like the changes, but you can still see missing episodes, but it has been moved to the 3 dot icon:

image.png.9fdac86cf462f258e9daa3248330ba86.png

  • 2 weeks later...
  • Replies 752
  • Views 178.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Are you running embyserver:beta ? I got the same error but only with the latest beta (4.6.0.34)   You can wait for a fix or specify the previous beta in Repository: emby/embyserver:4.6.

  • It's in the beta. Switch your repository to emby/embyserver:beta or wait for the next release.

  • alturismo
    alturismo

    may start like this   change UID > 99 GID > 100 remove GIDLIST <<<< delete this entry   check /mnt > edit > check if its read / wri

Posted Images

I went to update tonight and everything seemed to update as normal. However I am unable to get Emby to run. My log from the docker states:

text  error  warn  system  array  login  

Cannot get required symbol ENGINE_by_id from libssl
Aborted
Cannot get required symbol ENGINE_by_id from libssl
Aborted
Cannot get required symbol ENGINE_by_id from libssl
Aborted
Cannot get required symbol ENGINE_by_id from libssl
Aborted
Cannot get required symbol ENGINE_by_id from libssl
Aborted
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.

 

Any idea what's going on?

To anyone using EmbyServerBeta   There was an update about 8 hours ago which for me broke my emby

 

Cannot get required symbol ENGINE_by_id from libssl
Aborted
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[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.

** Press ANY KEY to close this window ** 


Temporary fix change repository from

 

emby/embyserver:beta


to

emby/embyserver:4.9.0.5


Emby will then start and run. Just in a few days when after a new version is up and issue is fixed we can just go back and set tag back to beta.

 

  • 3 months later...

Hey everyone. Whats the proper way to give my main emby account unraid permissions to delete files so I don't have to keep going into the terminal to do it.

22 minutes ago, blackbox said:

Hey everyone. Whats the proper way to give my main emby account unraid permissions to delete files so I don't have to keep going into the terminal to do it.

Hi there - in the Emby settings for your main user (or any user which you want to allow to delete files) have you turned that option on? In the web interface click on the cog on the top right of the page then USERS - select the main user then half way down the page is the option to allow media deletion.

 

Hope that helps.

Screenshot 2024-06-11 154631.jpg

11 minutes ago, Emneth Design said:

Hi there - in the Emby settings for your main user (or any user which you want to allow to delete files) have you turned that option on? In the web interface click on the cog on the top right of the page then USERS - select the main user then half way down the page is the option to allow media deletion.

 

Hope that helps.

Screenshot 2024-06-11 154631.jpg

Thanks for the reply. With that option selected I am getting this error.

Screenshot from 2024-06-11 10-58-58.png

Edited by blackbox

In your container variables make sure GID is 100, UID 99

Perhaps when you copied the movie to the folder it was set with the wrong permissions?

 

Have you tried going into the TOOLS page on Unraid and then chosen the "docker safe new perms" and run that which I think will change all the permissions so that they are uniform and you should then be able to delete then? Worth a try?

As Rick just said - make sure the GID and UID settings are right for Emby (on unraid Dashboard left click Emby and choose EDIT)

Screenshot 2024-06-11 162057.png

Edited by Emneth Design

Just made the adjustment. They were set at 2. Not sure why I did that. However, the same message still persists. even after a reboot of Emby and a full system reboot.

  • 1 month later...

Hi there, I am experiencing random crashes of the container. Seems to not be triggered my anything in particular. Following shutdown, container will not auto-start, but has to be manually started. Thanks in advance

 

text  error  warn  system  array  login  

Info App: Loading Fanart, Version=1.0.16.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Fanart.dll
Info App: Loading Tvdb, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Tvdb.dll
Info App: Loading MediaBrowser.Plugins.Anime, Version=1.5.6.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MediaBrowser.Plugins.Anime.dll
Info App: Loading OMDb, Version=1.0.21.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OMDb.dll
Info App: Loading playback_reporting, Version=2.1.0.5, Culture=neutral, PublicKeyToken=null from /config/plugins/playback_reporting.dll
Info App: Loading Emby.Api, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Web, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading MediaBrowser.Model, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading MediaBrowser.Common, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading MediaBrowser.Controller, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Providers, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Photos, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Server.Implementations, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.LiveTV, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.ActivityLog, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Server.MediaEncoding, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.LocalMetadata, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Notifications, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Web.GenericUI, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Codecs.Dxva, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Codecs, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Server.Connect, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading Emby.Server.Sync, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info App: Loading EmbyServer, Version=4.8.8.0, Culture=neutral, PublicKeyToken=null
Info SqliteUserRepository: Sqlite version: 3.42.0
Info SqliteUserRepository: Sqlite compiler options: ATOMIC_INTRINSICS=1,COMPILER=gcc-10.3.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_MATH_FUNCTIONS,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=127,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=1073741823,MAX_PAGE_SIZE=65536,MAX_SCHEMA_RETRY=25,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,OMIT_LOOKASIDE,SECURE_DELETE,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1
Info SqliteUserRepository: Opening sqlite connection to /config/data/users.db
Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal
Info SqliteUserRepository: PRAGMA foreign_keys=1
Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
Info ActivityRepository: Opening sqlite connection to /config/data/activitylog.db
Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal
Info ActivityRepository: PRAGMA foreign_keys=1
Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
Info NetworkManager: Detecting local network addresses
Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0
Info NetworkManager: GatewayAddresses: 192.168.240.1
Info NetworkManager: UnicastAddresses: 192.168.240.22
Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
Info NetworkManager: GatewayAddresses: 
Info NetworkManager: UnicastAddresses: 127.0.0.1
Info NetworkManager: Detected local ip addresses: [{"IPAddress":"192.168.240.22","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"}]
Info SqliteDisplayPreferencesRepository: Opening sqlite connection to /config/data/displaypreferences.db
Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal
Info SqliteDisplayPreferencesRepository: PRAGMA foreign_keys=1
Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
Info ServerConfigurationManager: Saving system configuration
Info App: Begin vacumming SqliteItemRepository
Info SqliteItemRepository: Opening sqlite connection to /config/data/library.db
Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal
Info SqliteItemRepository: PRAGMA cache_size=-2097152
Info SqliteItemRepository: PRAGMA page_size=4096
Info SqliteItemRepository: PRAGMA foreign_keys=1
Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
Error Main: Error in appHost.Init
        *** Error Report ***
        Version: 4.8.8.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.99-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Tue Jul 16 10:06:03 PDT 2024
        Framework: .NET 6.0.25
        OS/Process: x64/x64
        Runtime: system/System.Private.CoreLib.dll
        Processor count: 12
        Data path: /config
        Application path: /system
        SQLitePCL.pretty.SQLiteException: Corrupt: database disk image is malformed
        SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown.
           at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc)
           at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3_stmt stmt, Int32 rc)
           at SQLitePCL.pretty.StatementImpl.MoveNext()
           at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql)
           at Emby.Sqlite.BaseSqliteRepository.Vacuum()
           at Emby.Server.Implementations.ApplicationHost.VacuumDatabase(BaseSqliteRepository db)
           at Emby.Server.Implementations.ApplicationHost.VacuumDatabases()
           at Emby.Server.Implementations.ApplicationHost.RegisterResources()
           at Emby.Server.Implementations.ApplicationHost.Init()
           at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken)
        Source: SQLitePCL.pretty
        TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32)

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.

** Press ANY KEY to close this window ** 

 

Edited by GMAsterAU

1 hour ago, GMAsterAU said:

Hi there, I am experiencing random crashes of the container. Seems to not be triggered my anything in particular. Following shutdown, container will not auto-start, but has to be manually started. Thanks in advance

 

SQLitePCL.pretty.SQLiteException: Corrupt: database disk image is malformed

 

"database disk image is malformed" means your database is corrupted and needs to be replaced with a backup or recreated from scratch.

The application will not run until this is resolved.

 

Reason it happened is it possibly corrupted due to out of space at some point, or hardware issue.

Thanks for that. I am currently restoring it. Let's see what happens.

Hi all,

 

I might have a silly problem. I have been running the new EmbyServer Docker for a few months now, and I also have a Windows 11 VM with GPU passthrough on Autostart. Recently I found out that EmbyServer does not want to start up if the VM starts first and takes 'possession' of the GPU.

However, if disable the VM autostart and let EmbyServer start first (which it then does normally), and then manually start the VM after that, there is no problem, both work nicely in unison.

 

Any ideas on what this might be and how to resolve it? I tried putting EmbyServer at the top of the Docker starting order, but that does not seem to help. I can keep the VM autostart off, but I have a script that restarts my server every once in a while, and I feel there should be a way to make this work without having to manually start my Vm all the time.

1 hour ago, monden2 said:

and I also have a Windows 11 VM with GPU passthrough on Autostart.

which GPU do you have as passthrough device ?

 

as note, its always a either / or ... if a device is passed through, so i guess its a Nvidia or AMD Card, once the Card is passed through its only available to the VM and the Docker wont start as you have some variables bound to it ...

 

Alternative, start the VM with a user script with a dely of N, while N == xx seconds or whatever ...

 

but you should be aware, emby wont be able to do any hardware transcoding then anyway ... so another Alternative

 

remove the GPU feature from the docker as its not used anyway when you always have the VM running anyway ...

On 7/21/2024 at 2:58 PM, alturismo said:

which GPU do you have as passthrough device ?

 

as note, its always a either / or ... if a device is passed through, so i guess its a Nvidia or AMD Card, once the Card is passed through its only available to the VM and the Docker wont start as you have some variables bound to it ...

 

Alternative, start the VM with a user script with a dely of N, while N == xx seconds or whatever ...

 

but you should be aware, emby wont be able to do any hardware transcoding then anyway ... so another Alternative

 

remove the GPU feature from the docker as its not used anyway when you always have the VM running anyway ...

Hi alturismo,

 

I have a NVIDIA RTX 3070ti.

 

Where would I have to go in the docker to disable the hardware transcoding?

  • 1 month later...

Hi.

 

When I look at the Emby Server Dashboard, there is a message:

 

Emby Server 4.8.9.0 is Available for Emby NAS

Please shutdown Emby Server and install the latest version.

 

The Docker tab shows the Server is up to date, and a 'force update' does not pull anything down.  

 

Is this a spurious message or what do I need to do to update the the latest version?

(The docker's 'Repository' is set at emby/embyserver:latest 

 

Thanks.

3 minutes ago, Bob_C said:

Hi.

 

When I look at the Emby Server Dashboard, there is a message:

 

Emby Server 4.8.9.0 is Available for Emby NAS

Please shutdown Emby Server and install the latest version.

 

The Docker tab shows the Server is up to date, and a 'force update' does not pull anything down.  

 

Is this a spurious message or what do I need to do to update the the latest version?

(The docker's 'Repository' is set at emby/embyserver:latest 

 

Thanks.

As far as I am aware the developers know about this and have announced that they will release the appropriate docker version shortly :)

  • 3 months later...

Posted this in the binhex thread also. 

 

Anyone successful in enabling Tailscale within the Docker settings on Unraid 7? It throws this error for me/is unable to install the tailscale package. Just trying to launch the docker image with default settings+tailscale enabled. 

 

Running Unraid 7.0.0-rc.2 and the latest version of emby server. It works on most of my other apps, but Emby doesn't like it. 

 

image.png.ac9c2d820d8d7f6f0841279e7ac3d80f.png

Edited by eventorism

It did not work for me using the Official Emby. I switched to Linuxserver and it worked perfect.

 

Happy New Year!

 

I have not posted in a while.  It appears I can't start a new topic so I hope this location will suffice or that someone can place it in the appropriate place. 

I lost a password to duplicati 

Searching revealed that I need to pass the following command during startup:

--service-password=

 

With duplicati stopped, I went into duplicati>edit> and with the advanced option on I see:

Extra Parameters:

Post Arguments:

I attempted to use --services-passowrd= under "post arguments" and duplicati seemed to hang at startup.

I attempted to use --services-password= under "extra parameters" and duplicati disappeared from docker, but under app data it is still showing, so I did a manual add of duplicati and it seems everything is back.  

 

Where do I add this command to reset the password for duplicati

 

I could have added this to a section under post around duplicati, but I feel this is more about knowing where to pass commands then it is about duplicati.

 

Thanks,

Albin

Thanks!

 

I started duplicati and then opened the log file and clicked the provided link but nothing.  I changed the link to include my IP address instead of localhost, and it worked.  Thanks again.

 

Albin

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.