Search the Community

Hello, It's probably said many time, but what is the new way to update my emby-server without lose any config or data ? I don't want to lose special data (devices keys/hash not saved with the backup plugin) I'm run on Debian with an "apt-get" installation. No new version when i try the "apt-get update". Do you have a full procedure to upgrade to the further versions ?

So, I'm one of those emby users who paid for a lifetime, mostly just go along and run apt update as needed and let things run. Well, suddenly I'm seeing there's an update but I can't get via apt. Wierd. So I go looking, and there's a lot of random comments I can find on how you have to manually update to 3.4, and no repos in the foreseeable future. That's very annoying. But I could live with it. My issue is, there was no announcement I saw that this was coming. There was no 'you have an update, but it needs special attentioin' in the dashboard. And worst, I think, no clear place to find a good baseline of what you need to do to update. I find this to be a total customer service fail. It's also a minor to medium technical fail as so many people are having issues updateing. Me for instance. I can't get 3.4 to run stable. Often it'll run for a while, but randomly crashes. Sometimes I will start it and it claims the process is already started even tho ps -A | grep emby shows nothing. And I get constant apt errors complaining about libc-bin, even tho I appear to have the correct version installed. I'm on proxmox w/ a Debian 8 container. At this point I'm thinking of testing Plex out again. Although I may try to build a brand new debian 9 container. Either way, this is probably the clumsiest thing I've seen from the Emby team.

Good morning friends, since a couple of days i want to update emby server from 3.3x to 3.4 but it seems like 3.4 is not available in the repository. Is it intentionaly not beeing provided in the repo? If possible I would like to not use the .deb pakage and update/install via apt-get. Can you give a litle update on future plans here? Is the repo going to be updated or not? Thanks Soki

Hello, I noticed that this release did not appeared on the RPM Repo. Since it was mentioned that the RPM Repo is deprecated, I tried to install manually the RPM reported on the download pages, but it's failing on CentOS 6: --> Running transaction check ---> Package emby-server.x86_64 0:3.3.1.0-68.1 will be updated ---> Package emby-server.x86_64 0:3.4.1.0-1 will be an update --> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: emby-server-3.4.1.0-1.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.15)(64bit) for package: emby-server-3.4.1.0-1.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.16)(64bit) for package: emby-server-3.4.1.0-1.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.17)(64bit) for package: emby-server-3.4.1.0-1.x86_64 --> Processing Dependency: libm.so.6(GLIBC_2.15)(64bit) for package: emby-server-3.4.1.0-1.x86_64 --> Finished Dependency Resolution Error: Package: emby-server-3.4.1.0-1.x86_64 (/emby-server-rpm_3.4.1.0_x86_64) Requires: libc.so.6(GLIBC_2.15)(64bit) Error: Package: emby-server-3.4.1.0-1.x86_64 (/emby-server-rpm_3.4.1.0_x86_64) Requires: libm.so.6(GLIBC_2.15)(64bit) Error: Package: emby-server-3.4.1.0-1.x86_64 (/emby-server-rpm_3.4.1.0_x86_64) Requires: libc.so.6(GLIBC_2.16)(64bit) Error: Package: emby-server-3.4.1.0-1.x86_64 (/emby-server-rpm_3.4.1.0_x86_64) Requires: libc.so.6(GLIBC_2.14)(64bit) Error: Package: emby-server-3.4.1.0-1.x86_64 (/emby-server-rpm_3.4.1.0_x86_64) Requires: libc.so.6(GLIBC_2.17)(64bit) Maybe this one can work on CentOS7 only?

Good morning, after updating from 3.3x to 3.4 via dpkg I am missing several pictures. There are some folder pictures missing and a lot of pictures from media inside of all folders. Never had this problem before after an update. How to proceed from here? EDIT: Testet via different browsers and accounts, cleared cache of all testet browsers. EDIT2: Found several "Error ImageProcessor: Error encoding image" in server log. See attached. included server log.txt (changed url, private and public ips). Thanks in advance Soki Log.txt