Emby server partly inaccessible (ESET)

[lloskka 0]

Im starting to think, you dont care any of your customers at all.

 

Dont you think, we already tried?

 

Let me see, if throughout the day, we have a definitive fix / solution.

 

Then i will see if i maintain my few monthly subs  .

 

PS: Sorry for this hard language, but we are desperate...

[Passcratch 3]

Hi,

Have you tried with the IP address http://127.0.0.1:8096 or https://127.0.0.1:8920

It seems that the latest update of Windows crashes Localhost, I do not ais confirmation from them.

Edited March 26, 2016 by Passcratch

[Happy2Play 8296]

Does entering the machinename:8096 or localIP:8096 work?

 

 

Out of curiosity what version of Windows 10 are you on? v10586? Hit Windows key and type "winver".

Edited March 26, 2016 by Happy2Play

[NeonGOD 3]

It's the same..   tried all ip's 127.0.0.1, 192.168.1.2 & external too..  tried localhost

still the same

 

can access from all other machines on lan and from wan, but not from host machine..

 

im on Windows 10 build 10586.164

[lgvolvo 0]

Exactly the same for me. Nothing works.

Edited March 26, 2016 by lgvolvo

[anderbytes 139]

If the same Emby source code compiles the software in a way that localhost works with all Windows and Linux build with the exception of Windows 10, then it is 10 that needs patching, not Emby.

[Passcratch 3]

Ok, but strangely for me here I have only "http://localhost:8096"not responding

 

"http://127.0.0.1:8096"- working

"https://localhost:8920"- working

[anderbytes 139]

Do you have Antivirus or firewalls active? If yes... Deactivate them and try again, please.

 

Are you familiar with Wireshark? Maybe interface lo (localhost) can be sniffed to understand what is happening behind the curtains.

[NeonGOD 3]

yeah ofc i tried without Firewall & antivirus...

 

i try wireshark..

Edited March 26, 2016 by XenoBIT78

[Passcratch 3]

For you information, I have disabled both without success, I looked in the files of log antivirus and nothing suspicious.

I already had an earlier problem with the antivirus during updates application of the windows store (update bloked).

I uninstalled and reinstalled the antivirus and that solved my problem.

This solution that resolved my problem with emby too.

 

Thanks.

 

PS: My antivirus is Eset Nod32

[ebr 14930]

 

Im starting to think, you dont care any of your customers at all.

 

Dont you think, we already tried?

 

Let me see, if throughout the day, we have a definitive fix / solution.

 

Then i will see if i maintain my few monthly subs  .

 

PS: Sorry for this hard language, but we are desperate...

 

 

We are trying to help as much as we can (and several community members are chipping in as well) but it is almost impossible for us to diagnose local network issues.

 

Something is blocking your access to localhost.  This is done in some configurations of newer versions of Windows as a security feature.  This almost has to be something at a network level other than the app.

[anderbytes 139]

Okay. With the results we can see if Emby is sending the packages, and if any answer is received by server.

[yardameus 220]

I'm having the same issue, and entering machinename:8096 works.  Also, localipadddress:8096 also works.

 

Version 3.0.5920.0

 

Windows 10 version 1511 (os build 10586.164)

 

Google chrome Version 49.0.2623.87 m

[yardameus 220]

After I accessed it those two ways, the localhost way worked.  I hadn't done anything else.

 

Oh, and when accessing from those different ways, I had to the pop-up to allow notifications within Chrome and to store files locally.  

Edited March 26, 2016 by yardameus

[tvj28 3]

I had this same problem on two windows 10 pc's, turned out to be ESET, added the servers IP address to protocol filtering, excluded IP addresses and it's now fine.

[theojt 8]

Same issue here - I used the server last night and today it's kaput.

 

Eset is paused

Port is open

Others servers on the same machine exhibit no issues

Localhost, 127.0.0.1, and 198.162.2.198 all fail

Surprisingly, access from outside the network via Emby Connect works, so it must be a in house network issue

 

Out of ideas and its Saturday night - TV night

Edited March 26, 2016 by theojt

[Happy2Play 8296]

So does everyone that is having this problem have ESET on there system?  Since this isn't affecting everyone it has to be something with your setups and so far I would have to say it is an issue with ESET Security settings.

 

yardameus - no ESET

theojt - ESET

Passcratch - ESET

tvj28 - ESET

lgvolvo - ESET

Edited March 26, 2016 by Happy2Play

[yardameus 220]

No ESET here.  Also curious if the recent update fixed the issue for anyone.

[Happy2Play 8296]

No ESET here.  Also curious if the recent update fixed the issue for anyone.

Well from the couple logs posted everyone in on Stable 5882, except you.

[theojt 8]

I neglected to mention that I also upgraded to Windows 10 build 14295 (fast ring) today.  Anybody else?

[Happy2Play 8296]

I neglected to mention that I also upgraded to Windows 10 build 14295 (fast ring) today.  Anybody else?

 

So far two have reported standard release 10586.  Your the only one reporting fast ring 14295 so far.

 

 

Seems everyone is reporting external connections still work, so something locally is blocking the few that are having this issue, and I believe everyone is on Windows 10.

Edited March 26, 2016 by Happy2Play

[theojt 8]

Here is what posted to my browser after a long wait:

 

 

${TabDashboard} ${TabSettings}

 

${HeaderServerInformation}

 

 

 

 

 

${ButtonRestart} ${ButtonShutdown}

 

${HeaderActiveDevices}

 

${LabelCache}

${LabelLogs}

${LabelMetadata}

${LabelTranscodingTemporaryFiles}

${HeaderRecentActivity}

 

${HeaderLatestNews}

 

 

Emby ${LinkCommunity} ${LinkGithub} ${LinkApi}

Edited March 26, 2016 by theojt

[Happy2Play 8296]

That is the physical html page.  Sound like the Emby-Server folder needs to be whitelisted/exempted.

[theojt 8]

Added an Exclusion for Appdata\Roaming\Emby-Server in Eset - no difference.

 

I tried the Emby Service and it seems to start okay but I still can't get to the dashboard.

 

I did notice that there was an update to these Eset modules within the past 24 hours:

 

- Rapid Response Module 7727 (20160326)

- Advanced Antispam module 3443 (20160326)

 

Gonna have to leave this be for a while...thanks for the inputs.

[Sketchy 7]

The problem for me also turned out to be Eset's Nod32. It takes a lot of frustration to push me to to a forum for help, so thank you to all involved for getting me pointed in the right direction.

Edited March 27, 2016 by Sketchy