rhodges 49 Posted March 23, 2016 Posted March 23, 2016 One the same server, I can access http://x.x.x.x:8096 just fine. If I try that on a different computer (same network, plugged into the same switch) it won't work. If on the remote computer I used https://x.x.x.x:8920 it works. Very odd. It seems like it would be network related but I'm not sure what has changed. I only noticed it misbehaving today. I can telnet into it on 8096 and it connects but a web browser will just spin and eventually timeout. Version 3.0.5915.0 I disabled nod32 on the "client" and that didn't help. I verified the firewall is disabled on the server. I tried it on the latest Chrome and IE Edge. I don't have a different computer to try it on yet. It seems like it has to be my computer but what, I don't know.
Luke 42081 Posted March 23, 2016 Posted March 23, 2016 Hi, welcome. Did you resolve this issue? If not then please take a look at our Connectivity Troubleshooter. Please try the steps listed there and let us know if you're able to complete them all successfully, or which part you get stuck on. Thanks!
lloskka 0 Posted March 24, 2016 Posted March 24, 2016 (edited) Same problem over here. Me, no antivirus , firewall off. Both ports are open like usual in router .Tried 4 chrome, edge, iexplorer, and mozilla. same problem. Andddd tried an acronis .tib image, always worked What is happening? Can u indentify the problem?TTP/1.1 200 OK Server: Mono-HTTPAPI/1.0 Date: Thu, 24 Mar 2016 08:57:13 GMT Content-Length: 0 Connection: close Edited March 24, 2016 by lloskka
Luke 42081 Posted March 24, 2016 Posted March 24, 2016 Same problem over here. Me, no antivirus , firewall off. Both ports are open like usual in router . Tried 4 chrome, edge, iexplorer, and mozilla. same problem. Andddd tried an acronis .tib image, always worked What is happening? Can u indentify the problem? TTP/1.1 200 OK Server: Mono-HTTPAPI/1.0 Date: Thu, 24 Mar 2016 08:57:13 GMT Content-Length: 0 Connection: close HI, please take a look at our Connectivity Troubleshooter. Please try the steps listed there and let us know if you're able to complete them all successfully, or which part you get stuck on. Thanks!
rhodges 49 Posted March 24, 2016 Author Posted March 24, 2016 For me, the interesting part is that on my computer, if i access it with SSL, it works just fine. Also, my router running HAProxy with an SSL certificate that terminates SSL and proxys to the HTTP (not ssl) works just fine. On the server itself, it responds on the ip:port. I haven't tried another computer inside my network, but my one computer just won't acess it on http. I tried disabling AV, I tried different browsers, and even changed the http port number. I turned on fiddler, and I don't see any connection errors, just hanging. If I hit stop on the browser, I get some tokenized $SOMETHING type things on the screen, and inside the Emby logs, it is receiving the request, but something is just refusing to let it talk to my desktop. I will see if another computer fairs any better (I expect it will, because my router can talk to it on that IP/port without error). The thing is, it was working great. I don't know if a windows update or nod32 (even though I disabled it) happened. It is hard for me to believe it is Emby causing the issue, but until I point another computer at it, I haven't a clue.
rhodges 49 Posted March 28, 2016 Author Posted March 28, 2016 It was NOD32 that was the problem. Even pausing protection or turning of the web stuff didn't fix it. http://emby.media/community/index.php?/topic/32956-emby-server-partly-inaccessible/?p=316544
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now