Jump to content

Recommended Posts

Posted

What exactly is the problem?

 

The problem is that I cannot get Ubuntu unattended updates to update emby, but it works for other repositories.

Posted

Some distros are temporarily paused. We'll have the update out soon. Thank you for your patience.

I have been using the xUbuntu_Next release, but I noticed it has not been updated in a couple of months. I am going to switch to the 17.04 build since that is the Ubuntu release I am running, but I am curious. 

 

What is xUbuntu_Next intended for?

PremiumRed
Posted (edited)

I have Ubuntu 14 and I have been stuck on emby-server 3.2.25.11 since it was released...

Luke when do you think updates will be avaliable again for this distro? It’s been weeks???

 

 

JUST SEEN STABLE RELEASE UPDATED. Beta still doesn’t update tho

Edited by PremiumRed
Posted

I have Ubuntu 14 and I have been stuck on emby-server 3.2.25.11 since it was released...

Luke when do you think updates will be avaliable again for this distro? It’s been weeks???

 

They are available. You can see it right on our download page. The download page links to here:

https://software.opensuse.org/download.html?project=home%3Aemby&package=emby-server

 

Click grab binaries directly and it shows you the version number.

PremiumRed
Posted

Wow that was quick.. thanks for your reply

  • 4 weeks later...
Posted

We're looking into it, thanks.

Posted

We're looking into it, thanks.

 

FYI - CentOS repo has been down all day too, returning 404.

Posted

Packages appear to be back up, thanks.

  • Like 1
Posted (edited)

I am struggling with installing Emby at the moment. I have two almost identical Ubuntu 16.04 systems, one running the Mono beta installed using the offical package and the other server running the .Net Core version. I have removed the .Net Core Version of Emby on my server and am now trying to install the offical beta package but am getting the error:

Err:1 https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04  libembysqlite3-0 3.18.0+0-1.1
  Protocol "http" not supported or disabled in libcurl
Err:2 https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04  embymagick 6.9.6+6-7.1
  Protocol "http" not supported or disabled in libcurl
Err:3 https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04  emby-server-beta 3.2.30.19~beta-0+270.1
  Protocol "http" not supported or disabled in libcurl
E: Failed to fetch https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04/./amd64/libembysqlite3-0_3.18.0+0-1.1_amd64.deb  Protocol "http" not supported or disabled in libcurl

E: Failed to fetch https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04/./amd64/embymagick_6.9.6+6-7.1_amd64.deb  Protocol "http" not supported or disabled in libcurl

E: Failed to fetch https://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04/./all/emby-server-beta_3.2.30.19~beta-0+270.1_all.deb  Protocol "http" not supported or disabled in libcurl

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I have curl installed and the output of 'curl --version | grep Protocols' is

Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp

I am able to upgrade the packages on my other server just fine and have never had to install any addition depend ices to do so.

 

Output of 'curl https://google.com' is

<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="https://www.google.com/">here</A>.
</BODY></HTML>

 

Edited by Jdiesel
Posted

did you try the apt-get update?

Posted

did you try the apt-get update?

 

Yep apt-get update works fine, no errors updating the repository

Posted

I ended up forcing it to work by changing the "https" to "http" in the emby-server-beta.list

andrew.shields
Posted

I ended up forcing it to work by changing the "https" to "http" in the emby-server-beta.list

I am having exactly the same issue

how were you able to force it to work?

Posted

I am having exactly the same issue

how were you able to force it to work?

 

I edited the "https" to "http" file "/etc/apt/sources.list.d/emby-server-beta.list" or "/etc/apt/sources.list.d/emby-server.list" 

Posted

I am having exactly the same issue

how were you able to force it to work?

 Have you installed the .Net Core test server at any point?

Posted (edited)

I have Ubuntu 17.04 running on an old laptop, and with help from here I manged to get all my music files mounted in the /mnt/WinShare/Media/Music folder so that the emby server could see them.

 

Now , after a week or so of not using the emby server, when I load emby up in a web page, no music is showing. I then checked the Music folder, and it was empty, nothing there, no music files or folders.

 

I then checked the /etc/fstab file and the mount path is still there and as it was when I first typed it in.

 

Presently emby server loads to a blank music page with nothing sowing.

 

Any ideas as to what is wrong, as I have not changed anything. All I have done is take out the HD with Ubuntu on and replace with another HD to install another or different system. The Ubuntu HD is and has been installed for the last few weeks.

Edited by avalon65
Posted

I have Ubuntu 17.04 running on an old laptop, and with help from here I manged to get all my music files mounted in the /mnt/WinShare/Media/Music folder so that the emby server could see them.

 

Now , after a week or so of not using the emby server, when I load emby up in a web page, no music is showing. I then checked the Music folder, and it was empty, nothing there, no music files or folders.

 

I then checked the /etc/fstab file and the mount path is still there and as it was when I first typed it in.

 

Presently emby server loads to a blank music page with nothing sowing.

 

Any ideas as to what is wrong, as I have not changed anything. All I have done is take out the HD with Ubuntu on and replace with another HD to install another or different system. The Ubuntu HD is and has been installed for the last few weeks.

 

I would check your Emby library setup and make sure the paths are still accurate following the HD change. Then I would run a library scan. If the issue persists, please attach the emby server log. you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

thanks.

andrew.shields
Posted (edited)

I edited the "https" to "http" file "/etc/apt/sources.list.d/emby-server-beta.list" or "/etc/apt/sources.list.d/emby-server.list"

Working now, thanks

Edited by andrew.shields
Posted

I would check your Emby library setup and make sure the paths are still accurate following the HD change. Then I would run a library scan. If the issue persists, please attach the emby server log. you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

thanks.

 I checked the emby library setup on my ubuntu machine and the path to the music files is the same as before, but when I do a scan it doesn't and just puts it in a queue.

Edit: I have added another music folder as it were, and this time I just added it as /media/music, which is how it is in the FreeNAS ,

Jail / emby_1/add storage path.

Now doing a scan, but the spinning wheel is just going for what seems like forever.

Posted

 I checked the emby library setup on my ubuntu machine and the path to the music files is the same as before, but when I do a scan it doesn't and just puts it in a queue.

Edit: I have added another music folder as it were, and this time I just added it as /media/music, which is how it is in the FreeNAS ,

Jail / emby_1/add storage path.

Now doing a scan, but the spinning wheel is just going for what seems like forever.

 

Please attach the emby server log. you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

thanks.

Posted

I tried to attach a log file, but I got this message when doing so: Error You aren't permitted to upload this kind of file

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...