Debian

[civilmann 0]

Luke, there are 2 libraries that show up Movies and Movies1. They both show no content. In the main settings only one shows up it has the correct path to a Raid 1 array shared folder that has 500+ Movies in it. The files and folders on this array are also shared out via Samba so I can manage the files in it from my Windows 10 Desktop. I've tried reinstalling several times and during the install, there is a pause asking if I want to overwrite or keep the .conf file. I've tried both ways there also mentions during some of the installs something about privilege levels 0,1,2,3 and so on. I figured all of this would not be an issue as long as I create a library with correct pathing.  This has not worked so I back to the drawing board?

[civilmann 0]

Well, after vacillating back and forth between  3.2.33.0 and 3.2.36.0 I dumped all my libraries for the untold amount of times I get back to 3.2.33.0. I then rescan the library (one at this point) and all is working.

I then proceed to shut down the server (emby that is) but I notice a new update is available  3.2.40.0! I then proceed to the command line in a shell do the deed as indicated

(dpkg -i emby-server-deb_3.2.40.0_amd64.deb) and reboot. What do you know all is well it starts rescanning my only library and all of my files are present. I would stay away from  3.2.36.0 

just go straight to 3.2.40.0 works great! Thanks all for the comments.

Edited November 26, 2017 by civilmann

[Luke 40020]

Thanks for the feedback.

[Luke 40020]

Great news everyone. We now have .NET Core-based armhf .deb downloads ready for testing. If you'd like to try them out please see here:

 

https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core/

 

Thanks !

[adriy 0]

Hello, I have a lot of problem with my emby server. It can't load plugins list, load picture for metadata, ...

I see this error

System.Net.Http.CurlException: Problem with the SSL CA cert (path? access rights?)

 

But the owner dir of /opt/emby-server/ and /var/lib/emby is emby

 

The full log is here : https://pastebin.com/0cSh16pm

 

 

Regards

Edited December 9, 2017 by adriy

[adriy 0]

I stop the server and I launch emby with root

sudo service emby stop
cd /opt/emby-server/bin
/opt/emby-server/bin$ sudo ./emby-server

And It's work fine !

Can you help me to find the problem ?

 

Thank

[adriy 0]

I think it solve with

sudo setfacl -R -m g:emby:rx /etc/ssl/certs/

Edited December 9, 2017 by adriy

[Luke 40020]

Thanks for the feedback.

[maximuselefante 0]

Hello,

 

I am currently running emby on Debian 9.3 stretch and it works well but i have one issue: it refuses to run on startup.

 

I have it enabled but it seems as though it crashes on when my computer starts. I can then start it manually but I would prefer not to.

 

When I run "systemctl status emby-server" it has the readout of the attached file.

 

 

embyissues.txt

[Luke 40020]

Hi there @maximumuselefante, can you 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 !

[maximuselefante 0]

@@Luke Sorry about that 

 

Here is my log file

embyLog.txt

[Luke 40020]

Is this from when you ran it when the computer started? this appears to be a successful startup. thanks.

[maximuselefante 0]

Emby starts successfully with the commands to start it.

 

It fails to start automatically when I reboot my my computer even though I have it enabled to do so.

[Luke 40020]

Does it generate any log file when you do this?

[Luke 40020]

Just a heads up to anyone running an Emby Server beta package from OBS. In the next week or two we will be retiring the OBS beta channel.

 

Our website download page has been updated with beta install instructions:

 

https://emby.media/download

 

At your convenience it is recommended that you switch over to the new installation process as we will no longer be publishing betas to OBS. 

 

If you're running a non-beta (stable) package from OBS, you can continue to do so for the time being.

 

Thanks !

[maximuselefante 0]

@@Luke

 

I have attached the most recent log file as well as one that was labelled "unhandled" in the emby logs.

 

When I check the status of the service (after a reboot) I get the following:

root@elefante:/home/maximus# systemctl status emby-server
● emby-server.service - Emby Media Server
Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-01-22 16:33:02 EST; 42s ago
Process: 695 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS)
Process: 563 ExecStart=/usr/bin/emby-server start (code=exited, status=5)
Main PID: 563 (code=exited, status=5)

Jan 22 16:32:38 elefante systemd[1]: Started Emby Media Server.
Jan 22 16:32:39 elefante su[563]: Successful su for emby by root
Jan 22 16:32:39 elefante su[563]: + ??? root:emby
Jan 22 16:32:40 elefante su[563]: pam_unix(su:session): session opened for user emby by (uid=0)
Jan 22 16:33:02 elefante systemd[1]: emby-server.service: Main process exited, code=exited, status=5/NOTINSTALLED
Jan 22 16:33:02 elefante systemd[1]: emby-server.service: Unit entered failed state.
Jan 22 16:33:02 elefante systemd[1]: emby-server.service: Failed with result 'exit-code'.

EmbyLog2.txt

unhandled.txt

[Luke 40020]

Ok, that's resolved for the next release and should already be resolved on the beta channel. Thanks.

[tgessendorfer 7]

Running latest Emby Server 3.2.70 (Premiere) on Debian 9.3 and changed the public ports accordingly so that http will be mapped to 8096 for http locally and 443 to 8920 locally:

 

 

For me this looks good and the firewall (NAT device) is opened for http 80 and https 443, however I can still access the emby server via http on port 8096!?

 

I restarted the Debian machine (runs as VM in the Cloud btw) but still no access via port 80 and still 8096!? I am using public IP/DynDNS hostname to access externally.

 

What am I missing here? Debian firewall?

[dcrdev 254]

Running latest Emby Server 3.2.70 (Premiere) on Debian 9.3 and changed the public ports accordingly so that http will be mapped to 8096 for http locally and 443 to 8920 locally:

 

 

For me this looks good and the firewall (NAT device) is opened for http 80 and https 443, however I can still access the emby server via http on port 8096!?

 

I restarted the Debian machine (runs as VM in the Cloud btw) but still no access via port 80 and still 8096!? I am using public IP/DynDNS hostname to access externally.

 

What am I missing here? Debian firewall?

 

The public ports option(s) aren't indications that Emby will listen on those ports, they are there purely for mapping purposes in situations where one is doing nat forwarding from the local port to a differing port externally.

[tgessendorfer 7]

The public ports option(s) aren't indications that Emby will listen on those ports, they are there purely for mapping purposes in situations where one is doing nat forwarding from the local port to a differing port externally.

 

Arghh... got it... so I need to adjust the local ports right?

[henryford 11]

Just a heads up to anyone running an Emby Server beta package from OBS. In the next week or two we will be retiring the OBS beta channel.

 

Our website download page has been updated with beta install instructions:

 

https://emby.media/download

 

At your convenience it is recommended that you switch over to the new installation process as we will no longer be publishing betas to OBS. 

 

If you're running a non-beta (stable) package from OBS, you can continue to do so for the time being.

 

Thanks !

 

Just so I understand correctly: The new installation process is downloading the deb-packages manually and then installing? Because if so - that's too bad, the repository was really convenient for that.

[Luke 40020]

We may do a repository in the future but yes that is the process. Thanks.

[maiky jonathan gomes 0]

instead of entering the emby looks like invalid host, has formatted the machine anyway but continues in the same error.

instead of entering the emby looks like invalid host, has formatted the machine anyway but continues in the same error.

[Luke 40020]

instead of entering the emby looks like invalid host, has formatted the machine anyway but continues in the same error.

instead of entering the emby looks like invalid host, has formatted the machine anyway but continues in the same error.

 

Hi there, can you please describe the problem that you're having in more detail? Thanks !

[henryford 11]

We may do a repository in the future but yes that is the process. Thanks.

 

Thanks for the info!