Can't play videos

[WH4T. 0]

Hi Guys,

i have OMV 3.0.64 on my new NAS. Soo because a emby plugin isn't available yet I decided to install it with the commando line.

There Problem now is on any Client im not able to start a video. Just the web interface player is working.

I installed it with the Instructions for Debian and installed the key.

 

I tried following things:

giving the user emby admin

open tcp 8096 port

 

Scanning the data isnt a problem. The Problem is just the HTTP streaming.

 

Hopefully you can help me.

 

I attached several log files.

 

Greets 

Alex

emby.zip

[BAlGaInTl 288]

Hi Guys,

i have OMV 3.0.64 on my new NAS. Soo because a emby plugin isn't available yet I decided to install it with the commando line.

There Problem now is on any Client im not able to start a video. Just the web interface player is working.

I installed it with the Instructions for Debian and installed the key.

 

I tried following things:

giving the user emby admin

open tcp 8096 port

 

Scanning the data isnt a problem. The Problem is just the HTTP streaming.

 

Hopefully you can help me.

 

I attached several log files.

 

Greets

Alex

Have you considered running in Docker instead?

 

That's how I have mine running with OMV.

 

Sent from my A0001 using Tapatalk

[Luke 42077]

Hi, so if I understand correctly, it's working from the web app, but not the android app, is that correct?

[WH4T. 0]

The Web app is working. But android, kodi, and emby theater isn't working.

When i try to start streaming I get this error http://pastebin.com/B0ZD2Ct7.

 

I also tried Dockers, but i never used it before and i dont know how to set up the permissions for using folders outside the container.

When i tried to mount the folder in the dockers root, the mounted folder is empty.

[Luke 42077]

Hi there @@WH4T.

 

Can you please provide a log from the android app? You can learn how to do that here:

https://emby.media/community/index.php?/topic/15638-how-to-report-an-android-problem/

 

I notice you've updated to mono 4.8. Please note that we've only just begun testing with that. That could very well be the issue. thanks !

 

Thanks !