Fedora 22 support?

[spark 0]

I am using Fedora 22 Server and I failed to install emby-server many times.

 

First of all, EPEL is for RHEL and not for Fedora.

I cannot install EPEL at Fedora and it is not recommended to do it forcely.

 

dnf(yum) keeps me saying, "No package epel-release available" and when I use rpm file to install it, next step, fails to install emby-server

 

"Failed to open: /var/cache/dnf/epel-2b6dfc5904c26562/repodata/5d84887b1047f495701898ee370ff4a596147172c31d5e68d017979883ba763f-updateinfo.xml.bz2."

 

So I just removed the epel-release and install emby-server.

 

"

 Installed:

  ImageMagick.x86_64 6.9.1-13.1

  ImageMagick-libs.x86_64 6.9.1-13.1

  OpenEXR-libs.x86_64 2.2.0-1.fc22

  binutils.x86_64 2.25-9.fc22

  emby-server.noarch 3.0.5724.5-316.1

  ilmbase.x86_64 2.2.0-1.fc22

  libgdiplus0.x86_64 3.12-9.1

  libmonosgen-2_0-1.x86_64 4.0.3.20-3.1

  mailx.x86_64 12.5-15.fc22

  mono-core.x86_64 4.0.3.20-3.1

  mono-data.x86_64 4.0.3.20-3.1

  mono-data-oracle.x86_64 4.0.3.20-3.1

  mono-devel.x86_64 4.0.3.20-3.1

  mono-extras.x86_64 4.0.3.20-3.1

  mono-web.x86_64 4.0.3.20-3.1

  mono-winforms.x86_64 4.0.3.20-3.1

  patch.x86_64 2.7.5-1.fc22

  redhat-lsb-core.x86_64 4.1-29.fc22

  redhat-lsb-submod-security.x86_64 4.1-29.fc22

  spax.x86_64 1.5.3-4.fc22

 

Complete!

"

 

yeah I succeed to install emby-server package.

 

I also start the emby-server by "sudo service emby-server start" and it succeeded too.

 

The problem is that I cannot even connect to http://localhost:8096 or http://localhost:8096/web/wizardstart.html

 

What am I missing? What further can I try more?

 

Thanks.

[fc7 123]

Did you add a firewall rule to allow Emby traffic (ports 8096 and 8920 tcp)? You can also try stopping firewalld and confirm that indeed your problem is the missing firewall rules.

 

 

Sent from my iPhone using Tapatalk

[spark 0]

Yes of course.

Any other reason?

 

Thank you.

[fc7 123]

Yes of course.

Any other reason?

 

Thank you.

 

I know that many people will not like this, but you may want to try disabling SELINUX that is enabled by default in Fedora and CentOS.

Remember that after changing SELINUX configuration you need to reboot your server to apply the changes.

 

EDIT: this shouldn't make any difference but you shouldn't start Emby with the service command but use the systemctl command instead since Fedora uses systemd to handle the services. So to start Emby, first make sure it's not running and then do "sudo systemctl start emby-server".

Edited September 29, 2015 by fc7

[spark 0]

I already turned SELinux off.

 

I tried uninstalling the emby-server (dnf remove emby-server) (dnf is same as yum)

but it broke my system. Python or dnf(yum) never works. I cannot make any install because there are some dependencies lost.

 

I'd rather remove my OS and downgrade to Fedora 21.

 

Thank you

[fc7 123]

When I have some time I will test Fedora 22 package. That's one of the reasons why we are not announcing support for it yet. We couldn't test it.

[klen 2]

I was having trouble originally installing Emby-server in Fedora 22 (some earlier Emby version), but I just tried again with Version 3.0.5724.6 and it worked with the following settings (and fix):

repo:

[Emby]

name=Emby(Fedora22)

type=rpm-md

baseurl=http://download.opensuse.org/repositories/home:/emby/Fedora_22/

gpgcheck=1

gpgkey=http://download.opensuse.org/repositories/home:/emby/Fedora_22/repodata/repomd.xml.key

enabled=1

 

Install:

dnf install emby-server  <-- installs Emby and dependencies, but the server would not work (systemctl start emby-server failed)

according to /var/log/emby-server.log mono may have been causing the failure.  (I didn't save the exact error)

 

Dependancy fix:

recalling how the manual installation works, I installed mono-complete  (dnf install mono-complete)

 

Start and enable the service:

I then tried starting the app again systemctl start emby-server and it worked <-- don't forget to use root or super user privileges.

I enabled the service at startup systemctl enable emby-server and we are good to go

check with systemctl status emby-server

 

Hope that helps.