Jump to content

Problem with my server install


Seven_

Recommended Posts

Seven_

what i have noticed after watching a movie or a tv show was that the TV screen start flickering when going back to movie or tv section tab the screen start flickering

 

plus another problem that i see in logs

 

2019-07-07 20:38:44,427 DEBG 'emby' stdout output:

Error NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec': Error starting Ffdetect
*** Error Report ***

 

my system does not have a Nvidia card

Link to comment
Share on other sites

Hi, regarding the log message, that's just the way it looks in the log when you don't have that hardware. Nothing to worry about there.

 

Can you please attach the emby server log? Thanks.

Link to comment
Share on other sites

Seven_

Hi, regarding the log message, that's just the way it looks in the log when you don't have that hardware. Nothing to worry about there.

 

Can you please attach the emby server log? Thanks.

 

 

 here are the logs   

 

logs.7z

Edited by Seven_
Link to comment
Share on other sites

How did you install emby server? The startup command line looks wrong here. That is actually the reason for the ffdetect errors:

Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /config -ffdetect -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartexitcode 3
Link to comment
Share on other sites

Seven_

 

How did you install emby server? The startup command line looks wrong here. That is actually the reason for the ffdetect errors:

Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /config -ffdetect -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartexitcode 3

binhex-emby Docker container on Unraid, that cause the flickering as well ?

Edited by Seven_
Link to comment
Share on other sites

Can you switch to our official docker? That version is missing important elements, and yes it will cause flickering on Roku. Thanks.

Link to comment
Share on other sites

Seven_

Can you switch to our official docker? That version is missing important elements, and yes it will cause flickering on Roku. Thanks.

 

so i changed the to official EmbyServer (no flickering now), the problem i have now is that i can't use emby connect (port is open), and i also see this message  Check for plugin updates failed

 

WAN is not even appear in Dashboard, but like i say port 8096 is opened, can't add emby connect mail or user

Edited by Seven_
Link to comment
Share on other sites

Sounds like no internet connection on the docker container. Please attach an emby server log so that we can confirm. Thanks.

Link to comment
Share on other sites

Seven_

Sounds like no internet connection on the docker container. Please attach an emby server log so that we can confirm. Thanks.

 make no sense, he is able to pull metadata, i have tried on bridge mode, i get same result, but if i use my wan IP:port will display the login page, also i have tried from iOS over 4g using the WAN ip i will be able to add the server, but not if i am using emby connect, also in Dashboard>Alers i get Check for plugin updates failed

embyLog.txt

post-171088-0-12659600-1563029301_thumb.png

Edited by Seven_
Link to comment
Share on other sites

Yes look in the log. All outgoing requests are failing. Try using host networking mode.

Link to comment
Share on other sites

Seven_

Yes look in the log. All outgoing requests are failing. Try using host networking mode.

this is already in Host mode, on bridge mode i get same result

Link to comment
Share on other sites

Seven_

some update, i got a e-mail to confirm my account, my WAN Ip show up in the dashboard now, but still get those alerts Check for plugin updates failed

Link to comment
Share on other sites

I'm afraid I can't answer this for you because it is specific to your local configuration.

 

Something is blocking those outgoing requests. It could be your docker container configuration, firewall, security software, etc.

Link to comment
Share on other sites

Seven_

I'm afraid I can't answer this for you because it is specific to your local configuration.

 

Something is blocking those outgoing requests. It could be your docker container configuration, firewall, security software, etc.

ook, thank you for your help

Link to comment
Share on other sites

Have you considered trying our native Linux packages such as Ubuntu or Debian?

Link to comment
Share on other sites

Yes, it's just that it's running in a container vs. not having a container at all.

Link to comment
Share on other sites

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...