Search the Community

Hello, I install Emby server on Raspberry pi 4 with Dietpi distro. I have also installed there Nextcloud as my NAS server. There's very easy way to install SSL certificate for Nextcloud. I make a domain myserver.ddns.net on NO-IP website, install certbot and run letsencrypt from dietpi-software. Now I want to add SSL for my Emby Server. I see there's tutorial but I don't know nothing about certificates and don't want to brake something. @@pir8radio @@Swynol Can somebody tell me do I have to make another domain with ddns? There's also information on the tutorial beginning to kill all process on port 80. When I enable https for nextcloud I delete rule for port forwarding on my router for port 80 but when I make command: `netstat -nlp | grep :80` ``` tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1191/kodi.bin_v8 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1032/lighttpd tcp6 0 0 :::8096 :::* LISTEN 26999/EmbyServer tcp6 0 0 :::8080 :::* LISTEN 1191/kodi.bin_v8 tcp6 0 0 :::80 :::* LISTEN 1032/lighttpd ``` Regards Przemek

Hello, I currently run my emby server on a rasberry pi that is running the diet pi OS. When I go to my emby server dashboard it says I need to upgrade emby-server to 3.5, but when I run apt-get update or apt-get upgrade it says that emby-server is already at its newest verson... Is there no package for diet pi at the moment for version 3.5? I know that it was migrated from mono to dot net core, so I'm wondering if I need to do a clean install in order to upgrade to the newest verson.

Hi. I was running Raspbian on my pi and everything was fine but I changed to diet pi and I seem to be missing something. Setup: Ras pi 4 running DietPi v6.32.2, everything is updated. Emby 4.5.0.50. Issue: media can direct play on phone and pc. The server connects to the chrome cast, metadata casts, but as soon as I try to play something nothing happens (on either my first or second gen). I suspected that I was missing ffmpeg to allow Emby to convert the files to supported type for chrome cast but after installing from DietPi the config nothing changed. Proceeded to uninstall and reinstall Emby and still no change. any help would be appreciated. Thanks. embyserver.txt hardware_detection-63736897696.txt embyserver-63736897683.txt

Hi all, I am a satisfied user of Kodi and Emby. I run 2 Kodi's both on a seperate Pi 3b+ and have an Emby Server running also on a Pi 3b+ All the Pi's are 24/7 on so I quick fire up a movie when I want to, and alway's have the latest up-to-date movie information in Kodi. The thing is, that frequently when I start a movie, and select a subtitle with Kodi Kore app on my smartphone, the sub is not showing. A reboot is needed to fix this. Anyone has anyone experienced this before? Kind regards, - Libreelec 9.0.2 - Emby 4.1.12 - Emby server 4.2.0.40

Hey, I'm trying to configure an Emby server on a RPI3 running DietPi. My media is on a Seagate Personal Cloud NAS, and I was able to mount it using the DietPi disk manager on /mnt/segate, but somehow when I try to configure the library on Emby it doesn't recognize any media. It recognizes the path, but doesn't load anything. I think it's not a misconfiguration on the NAS mount because all other instances installed on DietPi can access the folder. Any thoughts?

I've been having a problem lately with emby crashing on a Raspberry Pi on DietPi. It ran almost without fault for the last year or so. After an upgrade from 3.3x to 3.5.2, it began crashing within minutes of starting it. So, I wiped the system and started over completely with a new install of DietPi and Emby as well. I'm not totally sure what's causing it, but I've been trying to run the Roku "create thumbnails" scheduled task, and it invariably crashes, even if I don't access the system in any other way. I've attached a copy of the log file, and the linux error status is also posted below. Any help would be greatly appreciated. ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: enabled) Active: failed (Result: signal) since Tue 2018-12-18 20:07:35 EST; 1h 47min ago Process: 6526 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 6526 (code=killed, signal=ABRT) Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Sqlite compiler options: COMPILER=gcc-6.4.1 20170707,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENA BLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY ,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Dec 18 19:14:28 DietPi emby-server[6526]: Info App: PRAGMA synchronous=1 Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.082916 seconds Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0145443 seconds Dec 18 19:14:28 DietPi emby-server[6526]: Info App: All entry points have started Dec 18 20:07:34 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Dec 18 20:07:35 DietPi systemd[1]: emby-server.service: Unit entered failed state. Dec 18 20:07:35 DietPi systemd[1]: emby-server.service: Failed with result 'signal'. log.zip