Search the Community

Hi everyone, I'm trying to get fail2ban working for Emby / Docker. Currently running in Ubuntu Mint Ubuntu 24.04 and have docker set to map the /config/logs directory to a local folder on the host. As far as I can tell I've got everything setup right but the filter is not matching anything it seems and it never logs failed logins to the jail. Also I don't recall where I noted them but I did see some weird charters in some kind of fail2ban logs for Emby. They were non-printable or invisible characters but I don't know that those would affect the regex especially since the manual regex test is passing. Does anyone have any ideas or see something overly obvious that I'm missing? Also worth nothing I manually tested the regex pattern and it matches. Docker Compose to map logs to local directory version: "2.3" services: emby: image: emby/embyserver:beta container_name: embyserver runtime: nvidia # Expose NVIDIA GPUs network_mode: host # Enable DLNA and Wake-on-Lan environment: - UID=1000 # The UID to run emby as (default: 2) - GID=1000 # The GID to run emby as (default 2) - GIDLIST=1000 # A comma-separated list of additional GIDs to run emby as (default: 2) #44,992 - NVIDIA_VISIBLE_DEVICES=all - NVIDIA_DRIVER_CAPABILITIES=compute,utility,video volumes: - /home/r3al/Desktop/Docker/Emby/programdata/:/config # Configuration directory - /media/r3al/New Volume/TT/TV/:/mnt/tv # Media directory - /media/r3al/New Volume/TT/Movies/:/mnt/movies # Media directory - /media/r3al/New Volume/TT/Live TV Recordings/:/mnt/mixed # Media directory - "/home/r3al/Desktop/Docker/Emby/logs/:/config/logs" ports: - 8096:8096 # HTTP port devices: # - /dev/nvidia-uvm:/dev/nvidia-uvm # Added nvidia devices here # - /dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools # Added nvidia devices here # - /dev/nvidia-modeset:/dev/nvidia-modeset # Added nvidia devices here # - /dev/nvidiactl:/dev/nvidiactl # Added nvidia devices here # - /dev/nvidia0:/dev/nvidia0 # Added nvidia devices here - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes - /dev/dri/renderD128:/dev/dri/renderD128 restart: on-failure /etc/fail2ban/filter.d/emby.conf [Definition] failregex = "http/1.1 Response 401 to ‌<HOST>" /etc/fail2ban/jail.d/emby.local [emby] enabled = true port = 8096 filter = emby logpath = /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt maxretry = 3 findtime = 600 bantime = 43200 Working manual regex test sudo fail2ban-regex /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt "http/1.1 Response 401 to ‌<HOST>" Manual Regex test returns Running tests ============= Use failregex line : http/1.1 Response 401 to ‌<HOST> Use log file : /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt Use encoding : UTF-8 Results ======= Failregex: 14 total |- #) [# of hits] regular expression | 1) [14] http/1.1 Response 401 to ‌<HOST> `- Ignoreregex: 0 total Date template hits: |- [# of hits] date format | [339] {^LN-BEG}ExYear(?P<_sep>[-/.])Month(?P=_sep)Day(?:T| ?)24hour:Minute:Second(?:[.,]Microseconds)?(?:\s*Zone offset)? `- Lines: 474 lines, 0 ignored, 14 matched, 460 missed [processed in 0.23 sec] Other troubleshooting things sudo systemctl status fail2ban ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset: enabled) Active: active (running) since Sat 2024-08-24 21:14:29 EDT; 16min ago Docs: man:fail2ban(1) Main PID: 51845 (fail2ban-server) Tasks: 7 (limit: 18710) Memory: 20.0M (peak: 21.5M) CPU: 5.311s CGroup: /system.slice/fail2ban.service └─51845 /usr/bin/python3 /usr/bin/fail2ban-server -xf start Sudo fail2ban-client status Status |- Number of jail: 2 `- Jail list: emby, sshd sudo tail -f /home/r3al/Desktop/Docker/Emby/logs/embyserver.txt 2024-08-25 01:30:00.040 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:30:00.040 Error Server: Access token is invalid or expired. 2024-08-25 01:30:00.040 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 3ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:35:00.122 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:35:00.122 Error Server: Access token is invalid or expired. 2024-08-25 01:35:00.122 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 2ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:36:59.424 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2024-08-25 01:40:00.076 Warn Server: AUTH-ERROR: 192.168.15.202 - Access token is invalid or expired. 2024-08-25 01:40:00.076 Error Server: Access token is invalid or expired. 2024-08-25 01:40:00.076 Info Server: http/1.1 Response 401 to ‌192.168.15.202‌. Time: 3ms. GET http://‌192.168.15.201‌:8096/Users/4ab54b48711e48a7af67df8da7a587db/Items/Latest?Limit=12&ParentId=4 2024-08-25 01:43:48.212 Info Server: http/1.1 POST http://‌media.eternaltek.xyz‌/emby/Users/authenticatebyname?X-Emby-Client=Emby Web&X-Emby-Device-Name=Safari iOS&X-Emby-Device-Id=cdf1ca5b-4fe1-453d-a08b-22539010875d&X-Emby-Client-Version=4.9.0.29&X-Emby-Language=en-us. Source Ip: ‌172.58.127.8‌, Accept=application/json, Connection=close, Host=‌media.eternaltek.xyz‌, User-Agent=Mozilla/5.0 (iPhone; CPU iPhone OS 18_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1, Accept-Encoding=gzip, deflate, br, Accept-Language=en-US,en;q=0.9, Content-Type=application/x-www-form-urlencoded; charset=UTF-8, Origin=‌https://media.eternaltek.xyz:23606‌, Referer=‌https://media.eternaltek.xyz:23606/web/index.html‌, Content-Length=12, X-TLS-Cipher=TLS_AES_128_GCM_SHA256, X-TLS-Protocol=TLSv1.3, X-TLS-SNI-Host=media.eternaltek.xyz, X-Real-IP=‌172.58.127.8‌, X-Forwarded-For=‌172.58.127.8‌, X-Forwarded-Proto=https, X-Forwarded-Port=23606, X-Forwarded-Host=‌media.eternaltek.xyz‌, X-TLS-Client-Intercepted=Unknown, sec-fetch-site=same-origin, sec-fetch-mode=cors, sec-fetch-dest=empty, priority=u=3, i 2024-08-25 01:43:48.212 Error DefaultAuthenticationProvider: Invalid username or password. No user named Dfv exists 2024-08-25 01:43:48.213 Error UserManager: Error authenticating with provider Default *** Error Report *** Version: 4.9.0.29 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.8.0-41-generic (buildd@lcy02-amd64-100) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2. OS/Process: x64/x64 Framework: .NET 8.0.6 Runtime: system/System.Private.CoreLib.dll Processor count: 10 Data path: /config Application path: /system System.Exception: System.Exception: Invalid username or password. at Emby.Server.Implementations.Library.DefaultAuthenticationProvider.Authenticate(String username, String password, User resolvedUser) at Emby.Server.Implementations.Library.UserManager.AuthenticateWithProvider(IAuthenticationProvider provider, String username, String password, User resolvedUser, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: System.Threading.Tasks.Task`1[MediaBrowser.Controller.Authentication.ProviderAuthenticationResult] Authenticate(System.String, System.String, MediaBrowser.Controller.Entities.User) 2024-08-25 01:43:48.213 Info UserManager: Authentication request for Dfv has been denied. 2024-08-25 01:43:48.214 Warn Server: AUTH-ERROR: 172.58.127.8 - Invalid username or password entered. 2024-08-25 01:43:48.214 Error Server: Invalid username or password entered. 2024-08-25 01:43:48.214 Info Server: http/1.1 Response 401 to ‌172.58.127.8‌. Time: 3ms. POST http://‌media.eternaltek.xyz‌/emby/Users/authenticatebyname?X-Emby-Client=Emby Web&X-Emby-Device-Name=Safari iOS&X-Emby-Device-Id=cdf1ca5b-4fe1-453d-a08b-22539010875d&X-Emby-Client-Version=4.9.0.29&X-Emby-Language=en-us

Im using Linux Ubuntu 16.04 64 bit and Asustor AS-604T ADM 3.2.1 This requires you do own a domain and have create a Lets Encrypt certificate! Following ports should be open: 80, 443, 8096 and 8920 1. Login to ADM web interface > Settings > Certificate Manager - Click on Export Certificate. 2. Extract certificate.zip and open the folder certifiate 3. right click in the folder - select open terminal 4. enter the command: * Please change the name of the give-me-a-name.pfx * After execution of this command you will be prompted to create a password, this is recommanded! openssl pkcs12 -export -out give-me-a-name.pfx -inkey ssl.key -in ssl.crt 5. Save the new create give-me-a-name.pfx file on your NAS in a shared folder of own choice 6. go to: http://local.ip.of.nas:8096/ 7. Go to Advanced and do the following Check that Allow remote connection to this Emby Server is marked. * add external domain name * Custon ssl certificate path (Click on the magnifier right to the text field and navigate to where the .pfx file is. * Certificate password - Add the password you entered after execution of step 4. * Secure connection mode - Set to preferred, but not required. 8. Hit save and navigate to Controlpanel > Restart - Now you should be able to access the Emby Media Server from outside.

hi! I have 4.8.3.0 installed using docker on Ubuntu Server 22.04.4 LTS. How do I troubleshoot an install that was previously working and decided to stop working? What I’ve confirmed is if I rename the root emby folder and force the server to recreate all its directories, the web interface comes up. If I put the old emby root directory back in place, the web server never starts. Here is the log file: 2024-04-20 00:19:59.630 Info Main: Application path: /system/EmbyServer.dll 2024-04-20 00:20:00.009 Info App: Setting default culture to en-US 2024-04-20 00:20:00.014 Info Main: Emby Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 2 Data path: /config Application path: /system 2024-04-20 00:20:00.014 Info Main: Logs path: /config/logs 2024-04-20 00:20:00.014 Info Main: Cache path: /config/cache 2024-04-20 00:20:00.014 Info Main: Internal metadata path: /config/metadata 2024-04-20 00:20:00.017 Info App: Emby Server Version: 4.8.3.0 2024-04-20 00:20:00.021 Info App: Loading assemblies 2024-04-20 00:20:00.072 Info App: File /config/plugins/Fanart.dll has version 1.0.16.0 2024-04-20 00:20:00.073 Info App: File /system/plugins/Fanart.dll has version 1.0.16.0 2024-04-20 00:20:00.073 Info App: File /config/plugins/MovieDb.dll has version 1.7.5.0 2024-04-20 00:20:00.073 Info App: File /system/plugins/MovieDb.dll has version 1.7.4.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/OMDb.dll has version 1.0.21.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/OMDb.dll has version 1.0.21.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/Emby.PortMapper.dll has version 1.2.4.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/Emby.PortMapper.dll has version 1.2.4.0 2024-04-20 00:20:00.074 Info App: File /config/plugins/EmbyGuideData.dll has version 1.0.13.0 2024-04-20 00:20:00.074 Info App: File /system/plugins/EmbyGuideData.dll has version 1.0.13.0 2024-04-20 00:20:00.075 Info App: File /config/plugins/StudioImages.dll has version 1.0.3.0 2024-04-20 00:20:00.075 Info App: File /system/plugins/StudioImages.dll has version 1.0.3.0 2024-04-20 00:20:00.075 Info App: File /config/plugins/MBBackup.dll has version 1.6.4.0 2024-04-20 00:20:00.075 Info App: File /system/plugins/MBBackup.dll has version 1.6.3.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/OpenSubtitles.dll has version 1.0.54.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/OpenSubtitles.dll has version 1.0.53.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/NfoMetadata.dll has version 1.0.80.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/NfoMetadata.dll has version 1.0.80.0 2024-04-20 00:20:00.076 Info App: File /config/plugins/Tvdb.dll has version 1.4.9.0 2024-04-20 00:20:00.076 Info App: File /system/plugins/Tvdb.dll has version 1.4.5.0 2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Dlna.dll has version 1.3.8.0 2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Dlna.dll has version 1.3.7.0 2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Webhooks.dll has version 1.0.35.0 2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Webhooks.dll has version 1.0.35.0 2024-04-20 00:20:00.091 Info App: Loading Fanart, Version=1.0.16.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Fanart.dll 2024-04-20 00:20:00.091 Info App: Loading MovieDb, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MovieDb.dll 2024-04-20 00:20:00.091 Info App: Loading OMDb, Version=1.0.21.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OMDb.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.PortMapper, Version=1.2.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.PortMapper.dll 2024-04-20 00:20:00.092 Info App: Loading statistics, Version=3.2.0.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Statistics.dll 2024-04-20 00:20:00.092 Info App: Loading EmbyGuideData, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /config/plugins/EmbyGuideData.dll 2024-04-20 00:20:00.092 Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /config/plugins/StudioImages.dll 2024-04-20 00:20:00.092 Info App: Loading MBBackup, Version=1.6.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MBBackup.dll 2024-04-20 00:20:00.092 Info App: Loading OpenSubtitles, Version=1.0.54.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OpenSubtitles.dll 2024-04-20 00:20:00.092 Info App: Loading NfoMetadata, Version=1.0.80.0, Culture=neutral, PublicKeyToken=null from /config/plugins/NfoMetadata.dll 2024-04-20 00:20:00.092 Info App: Loading Tvdb, Version=1.4.9.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Tvdb.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Dlna, Version=1.3.8.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Dlna.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Webhooks, Version=1.0.35.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Webhooks.dll 2024-04-20 00:20:00.092 Info App: Loading Emby.Api, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Web, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Model, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Common, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Controller, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Providers, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Photos, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Implementations, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.LiveTV, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.ActivityLog, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.MediaEncoding, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.LocalMetadata, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Notifications, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Web.GenericUI, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs.Dxva, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Connect, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Sync, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.092 Info App: Loading EmbyServer, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null 2024-04-20 00:20:00.400 Info SqliteUserRepository: Sqlite version: 3.42.0 2024-04-20 00:20:00.402 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 2024-04-20 00:20:00.402 Info SqliteUserRepository: Opening sqlite connection to /config/data/users.db 2024-04-20 00:20:00.417 Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal 2024-04-20 00:20:00.420 Info SqliteUserRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.508 Info ActivityRepository: Opening sqlite connection to /config/data/activitylog.db 2024-04-20 00:20:00.511 Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal 2024-04-20 00:20:00.511 Info ActivityRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.533 Info NetworkManager: Detecting local network addresses 2024-04-20 00:20:00.534 Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0 2024-04-20 00:20:00.534 Info NetworkManager: GatewayAddresses: 172.24.0.1 2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 172.24.0.2 2024-04-20 00:20:00.535 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo 2024-04-20 00:20:00.535 Info NetworkManager: GatewayAddresses: 2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 127.0.0.1 2024-04-20 00:20:00.602 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.24.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"}] 2024-04-20 00:20:00.606 Info SqliteDisplayPreferencesRepository: Opening sqlite connection to /config/data/displaypreferences.db 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.618 Info App: Adding HttpListener prefix http://+:8097/ 2024-04-20 00:20:00.671 Info AuthenticationRepository: Opening sqlite connection to /config/data/authentication.db 2024-04-20 00:20:00.673 Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal 2024-04-20 00:20:00.674 Info AuthenticationRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.690 Info SqliteItemRepository: Opening sqlite connection to /config/data/library.db 2024-04-20 00:20:00.698 Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA cache_size=-98304 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA page_size=4096 2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA foreign_keys=1 2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 2024-04-20 00:20:00.771 Info SqliteItemRepository: Init Complete 2024-04-20 00:20:01.109 Info App: Emby Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: system/System.Private.CoreLib.dll Processor count: 2 Data path: /config Application path: /system 2024-04-20 00:20:01.110 Info App: Logs path: /config/logs 2024-04-20 00:20:01.110 Info App: Cache path: /config/cache 2024-04-20 00:20:01.110 Info App: Internal metadata path: /config/metadata 2024-04-20 00:20:01.110 Info App: Transcoding temporary files path: /config/transcoding-temp 2024-04-20 00:20:02.422 Info FfmpegManager: FFMpeg: /bin/ffmpeg 2024-04-20 00:20:02.422 Info FfmpegManager: FFProbe: /bin/ffprobe 2024-04-20 00:20:02.422 Info FfmpegManager: FFDetect: /bin/ffdetect 2024-04-20 00:20:02.431 Info Skia: SkiaSharp version: 2.88.0.0 2024-04-20 00:20:02.433 Info ImageProcessor: Adding image processor Skia 2024-04-20 00:20:02.465 Info libvips: NetVips version: 2.3.1.0 2024-04-20 00:20:02.465 Info ImageProcessor: Adding image processor libvips 2024-04-20 00:20:02.533 Info TaskManager: Daily trigger for Emby Server Backup set to fire at 04/21/2024 00:10:00, which is 1429.9577930983332 minutes from now. 2024-04-20 00:20:02.535 Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 04/20/2024 02:00:00, which is 99.95774068666667 minutes from now. 2024-04-20 00:20:02.882 Info TaskManager: Daily trigger for Rotate log file set to fire at 04/21/2024 00:00:00, which is 1419.951958945 minutes from now. 2024-04-20 00:20:02.908 Info TaskManager: Queueing task HardwareDetectionScheduledTask 2024-04-20 00:20:02.912 Info TaskManager: Executing Hardware Detection 2024-04-20 00:20:02.923 Info App: ServerId: 90c28209f84a4d6eb5b35a58d8d192c7 2024-04-20 00:20:02.961 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Execute: /bin/ffmpeg -hide_banner -version 2024-04-20 00:20:02.992 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint 2024-04-20 00:20:03.000 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.032 Info FfmpegManager: FfmpegValidator.Validate complete 2024-04-20 00:20:03.219 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.226789 seconds 2024-04-20 00:20:03.223 Info App: Starting entry point Emby.Server.Implementations.Networking.RemoteAddressEntryPoint 2024-04-20 00:20:03.228 Info App: Loading data from /config/data/wan.dat 2024-04-20 00:20:03.233 Info App: Entry point completed: Emby.Server.Implementations.Networking.RemoteAddressEntryPoint. Duration: 0.0098643 seconds 2024-04-20 00:20:03.234 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint 2024-04-20 00:20:03.237 Info App: Loading data from /config/data/connect.txt 2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0 2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0 2024-04-20 00:20:03.239 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.005443 seconds 2024-04-20 00:20:03.240 Info App: Core startup complete 2024-04-20 00:20:03.250 Info App: Starting entry point MovieDb.Security.PluginStartup 2024-04-20 00:20:03.251 Info App: Entry point completed: MovieDb.Security.PluginStartup. Duration: 0.0009738 seconds 2024-04-20 00:20:03.251 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding 2024-04-20 00:20:03.252 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0008323 seconds 2024-04-20 00:20:03.252 Info App: Starting entry point MBBackup.ServerEntryPoint 2024-04-20 00:20:03.252 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 6.32E-05 seconds 2024-04-20 00:20:03.252 Info App: Starting entry point NfoMetadata.EntryPoint 2024-04-20 00:20:03.253 Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0006206 seconds 2024-04-20 00:20:03.253 Info App: Starting entry point Tvdb.EntryPoint 2024-04-20 00:20:03.253 Info App: Entry point completed: Tvdb.EntryPoint. Duration: 6.14E-05 seconds 2024-04-20 00:20:03.253 Info App: Starting entry point Emby.Webhooks.MigrationEntryPoint 2024-04-20 00:20:03.263 Info App: Entry point completed: Emby.Webhooks.MigrationEntryPoint. Duration: 0.002926 seconds 2024-04-20 00:20:03.263 Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint 2024-04-20 00:20:03.265 Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0016933 seconds 2024-04-20 00:20:03.265 Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint 2024-04-20 00:20:03.269 Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint. Duration: 0.0031783 seconds 2024-04-20 00:20:03.269 Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint 2024-04-20 00:20:03.270 Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0006636 seconds 2024-04-20 00:20:03.270 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup 2024-04-20 00:20:03.283 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264 2024-04-20 00:20:03.284 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4 2024-04-20 00:20:03.285 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx 2024-04-20 00:20:03.291 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4 2024-04-20 00:20:03.292 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx 2024-04-20 00:20:03.295 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0248056 seconds 2024-04-20 00:20:03.295 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint 2024-04-20 00:20:03.296 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0007693 seconds 2024-04-20 00:20:03.296 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake 2024-04-20 00:20:03.297 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0002309 seconds 2024-04-20 00:20:03.297 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier 2024-04-20 00:20:03.299 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0018423 seconds 2024-04-20 00:20:03.299 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier 2024-04-20 00:20:03.311 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0117179 seconds 2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard 2024-04-20 00:20:03.312 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0004591 seconds 2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents 2024-04-20 00:20:03.313 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0006732 seconds 2024-04-20 00:20:03.313 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier 2024-04-20 00:20:03.314 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0002695 seconds 2024-04-20 00:20:03.314 Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint 2024-04-20 00:20:03.317 Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0032508 seconds 2024-04-20 00:20:03.318 Info App: Starting entry point Emby.LiveTV.EntryPoint 2024-04-20 00:20:03.322 Info LibraryMonitor: Watching directory with new FileSystemWatcher for /userdata/kodi.ddb/movies for item 4514 2024-04-20 00:20:03.325 Info LiveTV: Loading live tv data from /config/data/livetv/timers 2024-04-20 00:20:03.328 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json 2024-04-20 00:20:03.348 Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0297033 seconds 2024-04-20 00:20:03.348 Info App: Starting entry point Emby.LiveTV.RecordingNotifier 2024-04-20 00:20:03.352 Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0033374 seconds 2024-04-20 00:20:03.352 Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint 2024-04-20 00:20:03.357 Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0049484 seconds 2024-04-20 00:20:03.357 Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint 2024-04-20 00:20:03.359 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0015033 seconds 2024-04-20 00:20:03.359 Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint 2024-04-20 00:20:03.363 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.376 Info Notifications: Registering event nofitier Emby Server User Notifications 2024-04-20 00:20:03.382 Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0227096 seconds 2024-04-20 00:20:03.382 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint 2024-04-20 00:20:03.385 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0026962 seconds 2024-04-20 00:20:03.385 Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint 2024-04-20 00:20:03.385 Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0002086 seconds 2024-04-20 00:20:03.385 Info App: All entry points have started 2024-04-20 00:20:03.468 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 qsvencdec -print_format json 2024-04-20 00:20:03.490 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code 0 - Succeeded 2024-04-20 00:20:03.560 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 nvencdec -print_format json 2024-04-20 00:20:03.566 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Process exited with code 1 - Failed 2024-04-20 00:20:03.917 Info CodecManager: CodecList: 2024-04-20 00:20:03.918 Info TaskManager: Hardware Detection Completed after 0 minute(s) and 1 seconds 2024-04-20 00:20:05.878 Info TaskManager: Queueing task PluginUpdateTask 2024-04-20 00:20:05.878 Info TaskManager: Executing Check for plugin updates 2024-04-20 00:20:05.881 Info TaskManager: Queueing task SystemUpdateTask 2024-04-20 00:20:05.882 Info TaskManager: Executing Check for application updates 2024-04-20 00:20:05.912 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json 2024-04-20 00:20:05.914 Info TaskManager: Queueing task SubtitleOcrDataTask 2024-04-20 00:20:05.914 Info TaskManager: Executing Download OCR Data 2024-04-20 00:20:05.946 Info TaskManager: Download OCR Data Completed after 0 minute(s) and 0 seconds 2024-04-20 00:20:06.157 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 seconds 2024-04-20 00:20:06.728 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 0 seconds and that’s it - it just halts after 6-7 seconds. Is there a way we can get the log file to be more verbose to see where it’s halting? Reminder: I can’t get into the web interface so we need to do this all on the command line. And another reminder: it doesn’t halt if I recreate the Emby root directories so it has something to do with my old library/config files (which currently is 100% stock, no extra plug-ins)

I created a brand new container and all my movies have .nfo files (created by Emby). Here is an example of metadata not being imported during the initial scan: <isuserfavorite>true</isuserfavorite> <playcount>2</playcount> <watched>true</watched> <lastplayed>2024-03-12 03:48:30</lastplayed> <resume> <position>2049.88</position> <total>7144.704233</total> </resume> When I created the Movie library, I made certain to check “nfo” as a metadata provider. What is the right way to configure Emby to import this metadata?

I’m planning to run Ubuntu on my mac mini instead of macOS. Has anyone made this transition? Is it is a straightforward process? Is it as easy as moving the database home directory to the Linux user? Will it be easy to map the new root directory given the entire file tree for all my movies, TV, and pictures are exactly the same? Anything else I should know before making the transition? Like are there any subtle differences in functionality of the server itself?

NB: This script only supports debian O/S, and debian based distributions (ubuntu etc). The script requires systemctl and apt which is present in all newer distributions. This script will probably not work as intended on Debian below v7 and Ubuntu below 14. A while back I created a script that will: Check if Apache and/or Nginx is running, and if running stop them. Disable UFW (firewall). Flush iptables. Check if certbot is installed, and if not, install it. Check if certificate is located in the emby directory, and if found, delete it. Ask for your FQDN of your emby server. Create a new certificate that's valid for 90 days. Convert the certificate to PFX and copy it to your emby directory. Ask for your emby group and user and change permissions of the PFX to the specified user (default is emby). Re-enable UFW (firewall). Re-enable Apache and/or Nginx (if it was stopped). Restart the Emby system service. After you have downloaded and placed the script on your server, you must unzip it and give the script execution permission. To do that, run the command: unzip embycert.zip && chmod +x embycert.sh This script should be run every 3 months to keep your certificate up-to-date. This script MUST be run as root with either SU or SUDO. SUDO is not native in Debian, and I would recommend to run this script it as root. NB: After installation, you must define the path to the certificate (under Network tab) which is: /var/lib/emby/emby.pfx and then again manually restart the emby server system service. Remember, if the FQDN is not typed correctly, the installation will fail, so be sure to spell it correctly, and make sure that the A record is valid and working. embycert.sh

Is there something wrong with Emby guide sources? Woke up this morning and I’m not able to pull Emby guide data… I noticed there was an Emby guide app update pushed yesterday too.

I removed a playlist from my provider (unrelated to the stations you see below), the next thing I know, I can't update my EPG. Despite everything still being mapped, I can't get my channel information restored. All that hard work. I even replaced a backup of my old TVxml file. I'm using a Linux seedbox (Ubuntu 20.04) with my Roku. I sent the logs through my Roku. I don't know if you guys need me to send my logs from my seedbox; but I can't on this public forum, as the logs contain my IP address as well as my seedbox DNS.

Hi there, im hoping someone could provide some guidance for me on my new Emby Premium docker build. It's working, however I have this issue that needs resolving. Im pretty new to the docker and linux world for that matter. The issue is; Cant delete movies and shows from the Emby UI. Error: "There was an error deleting the item from Emby Server. Please check that Emby Server has write access to the media folder and try again." Docker Compose running on Ubuntu 22.04.1 host. I've read and understood as much as I can of these articles. If I could, I would grant read/write/execute to 'emby', but that user doesnt exist on the Ubuntu host. The permissions that I do have assigned allows Emby to play the media because the server is working great for playing movies and shows. drwxrwxrwx+ 4 dan dan 4096 Nov 27 16:47 content (root folder in my user folder where my media is) drwxrwxrwx+ 25 root root 4096 Dec 2 06:13 downloads (subfolder of content) drwxrwxrwx+ 4 root root 4096 Nov 27 16:47 media (subfolder of content) I just updated the owner of the downloads and media folders to be dan dan, rebooted and that didnt help drwxrwxrwx+ 25 dan dan 4096 Dec 2 06:13 downloads (subfolder of content) drwxrwxrwx+ 4 dan dan 4096 Nov 27 16:47 media (subfolder of content) Emby server log attached, as well as my compose yml. Thank you for any help. embyserver.txt docker-compose.yml

Hello, i apologize i'm not sure to have the same problem but since version > 4.7.1 every day i have some crash also I notice this on my end : 2022-06-29 20:57:48.465 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0 - Succeeded 2022-06-29 20:57:48.474 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 4.7.5.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Linux version 5.10.0-15-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: opt/emby-server/system/System.Private.CoreLib.dll Processor count: 2 Data path: /var/lib/emby Application path: /opt/emby-server/system System.IO.IOException: System.IO.IOException: Read-only file system : '/mnt/share/xxxxxxxx.nfo' at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter) at Interop.CheckIo(Error error, String path, Boolean isDirectory, Func`2 errorRewriter) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode) After that the service is down.

Every day or so I have to stop/start Emby service as the main menu stops showing up on all devices (mobile, smart tv, desktop client). I run tail -f and watch the logs but after a while emby seems to no longer load the main menu (on now, live tv, etc no longer appear), no errors are appearing in the log files. relaunching apps have no effect only restarting Emby works. I've had Emby running for up to 2 or 3 days at time but lately it seems to die every 18-20 hours or so. I don't think it's the ubuntu box it's running on as radarr and sonarr don't seem to have this issue. I have gone for months without them having issues, same for the plex server that I am trying to get away from if I can get Emby to work as expected. I'm happy to provide logs but I don't see any errors being sent to the log when this happens, Emby just goes off to la la land. What do I need to check? Thanks in advance.

Hi, I have been having what seems to be a common issue which is the video player going to the start when attempting to skip. From what I could tell this has something to do with my Nginx reverse-proxy setup. Found out about this from this comment I went to their post and tried to use their Nginx reverse-proxy configuration. Post can be found here https://emby.media/community/index.php?/topic/93074-how-to-emby-with-nginx-with-windows-specific-tips-and-csp-options/ But I am getting a error every time I run it. I am unsure if this configuration is supposed to work on ubuntu as it is posted under general/windows and my server is on Ubuntu 20.04.4 LTS x86_64. The error is as follows This is the configuration used to achieve this error. https://pastebin.com/Vyfhkrb6 . I am also using cloud flare so take that into account when reviewing the configuration.

Hi I know this question has been asked numerous times, but I have already read two Emby connection guides and some other forum posts regarding the same issue to no avail. My issue is simply that I can't connect to my Emby server remotely. I have followed these guides: https://support.emby.media/support/solutions/articles/44001849007-connectivity https://support.emby.media/support/solutions/articles/44002137137-remote-setup Right now I'm stuck at the "traceroute" command, as I'm a bit unsure how to read the output: traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 2.382 ms 3.843 ms 3.798 ms 2 192.168.87.1 (192.168.87.1) 4.660 ms 4.830 ms 7.049 ms 3 100.76.0.2 (100.76.0.2) 8.531 ms 8.489 ms 9.729 ms 4 45.80.95.198 (45.80.95.198) 8.042 ms 8.280 ms 8.242 ms 5 45.80.95.224 (45.80.95.224) 9.490 ms 9.499 ms 9.460 ms 6 45.80.95.222 (45.80.95.222) 9.423 ms 5.053 ms 6.278 ms 7 * * * 8 89.184.134.238 (89.184.134.238) 16.229 ms 89.184.134.240 (89.184.134.240) 16.363 ms 16.335 ms 9 89.184.134.79 (89.184.134.79) 16.305 ms 16.277 ms 17.424 ms 10 212.10.11.15 (212.10.11.15) 17.382 ms 17.344 ms 17.312 ms 11 108.170.252.65 (108.170.252.65) 21.002 ms 108.170.251.129 (108.170.251.129) 18.483 ms 108.170.252.65 (108.170.252.65) 19.554 ms 12 142.250.236.37 (142.250.236.37) 14.808 ms 142.250.209.243 (142.250.209.243) 14.825 ms 142.250.225.77 (142.250.225.77) 14.691 ms 13 dns.google (8.8.8.8) 14.650 ms 14.868 ms 15.202 ms The site canyouseeme.org shows the correct IP (WAN) as is shown on my server dashboard. When entering the port 8096 or 8920 I get the message: "Error: I could not see your service. Reason: Connection timed out". Here are my other settings: Emby network settings Allow remote connections to this Emby Server (checked) Enable automatic port mapping (checked) Router information and settings NETGEAR Router Turn UPnP On (checked) Active Protocol Int. Port Ext. Port IP Address YES TCP 8096 8096 192.168.1.18 YES TCP 8920 8920 192.168.1.18 Server information Ubuntu 20.04.3 LTS LAN-connection

Hello, I can no longer invite users, when I click add user Emby Server does not bring up the dialog to Add Local User or Invite with Emby Connect. Has Emby Connect or inviting been removed again?

Hola amigo abro este hilo para explicar como instalar Emby en Ubuntu ya que dan por hecho que todo el mundo es un mega crack en linux. La verdad que es super facil y no se porque no lo ponen en la misma pagina de descarga el código de instalación por terminal. Para instalar Emby tenemos que pegar este codigo en nuestro terminal de Ubuntu sudo wget https://github.com/MediaBrowser/Emby.Releases/releases/download/4.4.3.0/emby-server-deb_4.4.3.0_amd64.deb && sudo dpkg -i emby-server-deb_4.4.3.0_amd64.deb En función de la versión que queramos instalar se tendrá que cambiar la versión, pongo otro ejemplo de una versión inferior. sudo wget https://github.com/MediaBrowser/Emby.Releases/releases/download/4.4.2.0/emby-server-deb_4.4.2.0_amd64.deb && sudo dpkg -i emby-server-deb_4.4.2.0_amd64.deb Si vais a la web de descarga de Emby https://emby.media/linux-server.html veréis que si ponéis el ratón encima del enlace os dará el enlace para modificar el código y así poder instalar la versión que vosotros queráis. Y para actualizar Emby se tiene que hacer instalando la versión que queráis, es decir Emby no se actualiza por si solo y tienes que reinstalar por encima no te preocupes que no se borrara nada de lo que ya tengáis.

Hi, I am in the process of a full library scan, and I see the following errors appear in the server logs repeatedly. System.Exception: ffprobe failed for file... streams and format are both null and [matroska,webm @ 0xebdc00] Format matroska,webm detected only with low score of 1, misdetection possible! [matroska,webm @ 0xebdc00] EBML header parsing failed : Invalid data found when processing input embyserver.txt

I've read through countless threads on this topic with similar situations and I cant find the solution. I have all my media on an external HD. When I'm setting up the server, I go to add a folder for the media, the file path doesn't show up. And when I manually type in the path I get; "The path could not be found. Please ensure the path is valid and try again.". How can I specifically grant emby:emby permissions to access my external? When I use; ls -l /path/to/media Every file is permissioned my username and my group. How can I change this? Thanks!

Its been a while since i used emby . So i thought to give the latest beta a try . I downloaded the latest beta from here - https://github.com/MediaBrowser/Emby.Releases/releases/download/4.6.0.28/emby-server-deb_4.6.0.28_amd64.deb and installed it . Then i enabled and started the service through systemctl sudo systemctl enable emby-server && sudo systemctl start emby-server But for some reason , the service is not running / crashing . sudo systemctl status emby-server returns the following ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-02-24 05:17:27 UTC; 28s ago Process: 49019 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS) Main PID: 49019 (code=exited, status=0/SUCCESS) Feb 24 05:17:27 xd003 emby-server[49019]: InnerException: System.Net.Sockets.SocketException: Address already in use Feb 24 05:17:27 xd003 emby-server[49019]: Source: System.Net.Sockets Feb 24 05:17:27 xd003 emby-server[49019]: TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(System.Net.Sockets.SocketError, System.String) Feb 24 05:17:27 xd003 emby-server[49019]: at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) Feb 24 05:17:27 xd003 emby-server[49019]: at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) Feb 24 05:17:27 xd003 emby-server[49019]: at System.Net.Sockets.Socket.Bind(EndPoint localEP) Feb 24 05:17:27 xd003 emby-server[49019]: at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() Feb 24 05:17:27 xd003 emby-server[49019]: Feb 24 05:17:27 xd003 emby-server[49019]: Info Main: Shutdown complete Feb 24 05:17:27 xd003 systemd[1]: emby-server.service: Succeeded.

Hi, I have created this in the hope it helps others. It isn't very detailed but hopefully enough information to be helpful. Thank you. My setup: Ubuntu 20.04.1 LTS (I would prefer if this said CEntOS but that's another story) TurboSight TBS 6280 DVB-T/T2/C (SAA716x dvb adapter) Docker (I don't think this effects my guide much below but worth mentioning) Emby (emby/embyserver:latest version on as of 9th January 2021) Tvheadend (linuxserver/tvheadend:latest version on as of 9th January 2021) docker-compose.yml Install required software (Ubuntu, TBS drivers, docker, docker-compose) Check DVB adapter exists $ ls /dev/dvb/ Install required Docker images/containers (see attached docker-compose.yml) $ docker-compose up -d http://tvheadend:9981 (setup Tvheadend) Configuration > Start wizard > Language (save and next) > Access control details (either on this screen or after the wizard create a user with the username * and no password (see attached User login.png) Tuners and network (configure as required) Assign Predefined Muxes to Networks (configure as required) > Scanning (save and next) > Map services to channels (configure as required) > Finish http://emby:8096 (setup Emby) Settings > Live TV > Live TV > TV Sources > M3U Tuner (http://tvheadend:9981/playlist/channels.m3u) Settings > Live TV > Live TV > TV Guide Data Providers > Guide Data Setup (configure country as required) and Guide source: XmlTV > File or URL (http://tvheadend:9981/xmltv/channels) Settings > Users > Access > Recordings Notes: Recordings made through the Tvheadend interface are separate to recordings made through the Emby interface. If I haven't mentioned a setting, chances are I haven't changed from the default. Multiple screen shots are attached to help clarify some steps. The M3U link can be tested in VLC media player: Media > Open Network Stream > network URL: http://tvheadend:9981/playlist/channels.m3u The channels link can be tested in an internet browser by pasting the link into the address bar. http://tvheadend:9981/xmltv/channels I hope this helps someone docker-compose.yml

Inspired by this article on how to host a website using cloudflare and nginx, i intend to do the same for my emby server. Like swynol, i have nginx server and emby server running on the very same machine which i station on my local home network. My OS however is ubuntu instead of windows. Ive tried both swynol's and lukecarrier's github codes, no avail, it wont redirect to the emby server no matter what. My nginx server was indeed running as both ports 80 and 443 are opened as tested by canyouseeme.org. It just wont redirect whenever i go to https://emby.mydomainname.com I dont even know where should i put the code, of the guides online, some say /etc/nginx/conf.d/mydomain.com, some say /etc/nginx/sites-available/mydomain.com with /etc/nginx/sites-enabled linked to earlier. I highly suspect that the code is the culprit. sudo nginx -t show no error, systemctl status nginx operational Shed some light anyone? Appreciate it. Update 16/12/2020 Here's my nginx code where I put under sites-available and then linked to sites-enabled via ln -s server { listen [::]:80; ## Listens on port 80 IPv6 listen 80; ## Listens on port 80 IPv4 listen [::]:443 ssl http2; ## Listens on port 443 IPv6 with http2 and ssl enabled listen 443 ssl http2; ## Listens on port 443 IPv4 with http2 and ssl enabled proxy_buffering off; ## Sends data as fast as it can not buffering large chunks. server_name emby.mydomainname.com; ## enter your service name and domain name here access_log /var/log/nginx/embyaccess.log; ## Creates a log file with this name and the log info above. ## SSL SETTINGS ## ssl_session_timeout 30m; ssl_protocols TLSv1.2 TLSv1.1 TLSv1; ssl_certificate /etc/ssl/mydomainname/cert.pem; ## Location of your public ssl_certificate_key /etc/ssl/mydomainname/key.pem; ## Location of your private PEM file. ssl_client_certificate /etc/ssl/mydomainname/cloudflare.crt; ##Authenticated Origin Pulls ssl_verify_client on; ##Authenticated Origin Pulls ssl_session_cache shared:SSL:10m; location ^~ /swagger { ## Disables access to swagger interface return 404; } location / { proxy_pass http://localhost:8096; ## Enter the IP here proxy_hide_header X-Powered-By; ## Hides nginx server version from bad guys. proxy_set_header Range $http_range; ## Allows specific chunks of a file to be requested. proxy_set_header If-Range $http_if_range; ## Allows specific chunks of a file to be requested. #proxy_set_header X-Real-IP $remote_addr; ## Passes the real client IP to the backend server. proxy_set_header X-Real-IP $http_CF_Connecting_IP; ## if you use cloudflare un-comment this line and comment out above line. proxy_set_header Host $host; ## Passes the requested domain name to the backend server. proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; ## Adds forwarded IP to the list of IPs that were forwarded to the backend server. ## ADDITIONAL SECURITY SETTINGS ## ## Optional settings to improve security ## ## add these after you have completed your testing and ssl setup ## ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ## ## See https://hstspreload.org/ read through the "Deployment Recommendations" section first! ## add_header 'Referrer-Policy' 'origin-when-cross-origin'; add_header Strict-Transport-Security "max-age=15552000; preload" always; add_header X-Frame-Options "SAMEORIGIN" always; add_header X-Content-Type-Options "nosniff" always; add_header X-XSS-Protection "1; mode=block" always; ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client. proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; } } Big thanks to @pir8radio for the configuration, my configuration is based on his. Setting up authenticated origin pulls is optional, here's where I download the cert. https://support.cloudflare.com/hc/en-us/articles/204899617-Authenticated-Origin-Pulls#section6

Hi all, I've run into an unusual problem with Emby - one of my libraries is empty, and repeated scans do not seem to be repopulating it. Debug log covering a requested library scan is attached to this post. Details: Server is running Ubuntu 20.04.1LTS; problem occured on Emby 4.4.3 and remains the same on 4.5.3 as well. I currently have 9 libraries on the system, scattered over several HDDs: - 12TB_D1 holds "Ongoing TV", "Unwatched TV" and "Archived TV" Libraries - no problems - 8TB_D1 holds "Anime Series", "Anime Movies", "Music" and "Soundtracks" Libraries - no problems - 12TB_D3 holds "Movies" and "Unwatched Movies" Libraries. "Movies" is fine; populated normally, no issues. "Unwatched Movies" appears completely empty. Here's a complicating factor: Until a week or two back, both "Movies" and "Unwatched Movies" were stored on a different HDD. I moved the files across, and updated the Library settings from the Emby Server Dashboard by adding the new folders to each library, then deleting the old folders. This worked for "Movies" but apparently not for "Unwatched Movies". I spotted the problem a couple of days ago (i.e. several days after the switchover), and tried deleting the "Unwatched Movies" library in it's entirety and creating a new one with the same name - no change, nothing found on scan. I've checked permissions - ownership and permissions are identical between "Movies" and "Unwatched Movies" and their content. I've created a Test Library as a new item and pointed it at the same folder, but it remains empty after a media scan, so I don't think it's a corrupted item in a database caused by using the same name for a "different" library. Any thoughts or suggestions for the next step in troubleshooting would be appreciated. Thanks. embyserver.txt

My Ubuntu 18.04.5 broke with Emby-server 4.4.0.40. All media files are on other discs. New Ubuntu has 20.04.1 and I have downloaded Emby-server 4.5.3.0. I have access to a backup copy of the original /var/lib/emby from 4.4.0.40. If I install the new Emby-server 4.5.3.0 can I simply restore the /var/lib/emby from 4.4.0.40 to get up and running or are the contents of the /var/lib/emby folder incompatible? Thanks, NCBillP

I installed emby in Ubuntu Bionic Beaver. Installation page for Live TV doesn't detect the usb tv tuner. Hauppauge WinTV-HVR-955Q I know it works because Kaffeine is running it fine. . . Anything you can suggest to get this device to run on the Media Server? -K

Context : I am using a very old laptop running pop OS 20.04 and docker . I have a 3rd gen i7 on this and an nvidia 740m GPU. I installed graphics driver from ubuntu repository and my discreet GPU works (image attached for clarity) because I can see kodi picking up the discreet GPU. Problem : I installed emby beta 4.5.0.20 from dockerhub and installed nvidia container runtime and loaded the systemd module on it : nirjhor@pop-os ~/Downloads [1]> sudo cat /etc/systemd/system/docker.service.d/override.conf [Service] ExecStart= ExecStart=/usr/bin/dockerd --host=fd:// --add-runtime=nvidia=/usr/bin/nvidia-container-runtime nirjhor@pop-os ~/Downloads> Now when I load emby I see my intel processor but not nvidia (image attached) Docker command I used : sudo docker run -d --volume /home/nirjhor/emby/config:/config --volume /home/nirjhor/Videos/Movies:/media/movies --volume /home/nirjhor/Videos/TV:/media/tv --net=host --device /dev/dri:/dev/dri --runtime=nvidia --publish 8096:8096 --publish 8920:8920 --env UID=1000 --env GID=100 --env GIDLIST=100,44,106 emby/embyserver:beta I get the value of render and graphics by this : nirjhor@pop-os ~/Downloads> getent group video | cut -d: -f3 44 nirjhor@pop-os ~/Downloads> getent group render | cut -d: -f3 106 nirjhor@pop-os ~/Downloads> Now my question is, how do I get this nvidia card to work? I took a look at linuxserver.io and I believe they expose nvidia somehow differently, which I did not understand quite well. Adding embyserver log for good measure. Goes without saying, I have premier. For what it's worth, in my desktop computer running arch linux I followed this exact steps and now have nvidia NVENC working. So I am even more clueless as to what I might be doing wrong. Please help. embyserver.txt

I'm hosting version 4.4.3.0 of Emby on Ubuntu 20.04.1. I have a multi-episode file that includes the final episode of season 3 and the first episode of season 4, but Emby marks S04E01 of the show as missing. I have tried the naming format included in the screen shot and an officially supported convention ('Star Trek The Next Generation S03x26.S04x01.mp4') listed in the TV Naming guide, but Emby still marks the episode as missing. Does this (or any) version of Emby support multi-episode files that are split between two seasons? If not, is there a way I can manually mark it as present and point it to that file? If not I'll likely just add a symlink to the file and name it as S04E01 so Emby will recognize it as present.