Tonos 6 Posted April 2, 2015 Posted April 2, 2015 I was hoping I could get some help on this issue that has popped up all of a sudden with Emby Classic 3.0.258 (WMC). For some reason my client will not connect at all to my server (v3.0.5569.0). The only change I had made to my setup was the upgrade of my server to this version yesterday. The client had been running fine for the past day or so. The issue started after I had fully exited the client and tried to reconnect. It sits there for about 5 or so seconds before displaying the pin verify screen for MB Connect. Im assuming this is because it cannot find the server. After re-trying several times I disabled the firewall momentarily on my server and immediately it re-connected. You would think this would point to a misconfigured server firewall? However I have had a working rule up and running for quite a while now, so it has got me beat. Emby Theatre 3.0.5569.2448 works fine from the same machine.. The web client using chrome also works fine from any device on my network. The iOS and Android clients also all work no problems. I usually run the server as a service, and my original firewall rule allowed connectivity only to the service It worked fine for long time. I have also tried running the server from the shortcut with no difference. My current firewall now has a rule which just allows TCP 8096 The firewall has been reset several times (server OS is Server2012 R2, client is Win 7 x64) and doesn't appear to be dropping any packets. Except for a few on port 1900 which I believe is an unrelated SSDP service? I couldnt see too much in the logs but here they are anyway. Its like the server is ignoring the client requests?? Emby Classic client https://www.dropbox.com/s/665qjvxa9zszs57/MBClassic-242015e6d7842ace7c46bab6f959327ce021f1.log?dl=0 Server (the client ip is 192.168.2.24) https://www.dropbox.com/s/67oxv9g8o3zre2h/server-63563614778.txt?dl=0 Anyway, more than likely it is something wrong with my setup - hope anyone has some pro tips! And lastly, it probably doesnt help much, but attached is a screenshot of the 2 clients on the same machine - with different results on connect. Thanks!
ebr 16173 Posted April 2, 2015 Posted April 2, 2015 If disabling the firewall fixes it then it is definitely a problem with the firewall rules. Confirm they are correct.
Tonos 6 Posted April 2, 2015 Author Posted April 2, 2015 Thanks for quick response.. Ive looked at the firewall rules pretty closely and im out of any other ideas. Port 8096 and the https port 8920 are currently wide open, which seems to make Theater and the Web client function. Strangely, if I turn off the server firewall, log in Emby classic, then re-enable the firewall, everything is sweet. Can I confirm if there are any other ports ive missed that are needed by Emby classic? especially at logon. -Anthony
CashMoney 94 Posted April 2, 2015 Posted April 2, 2015 Other have had this (or a similar) issue in the past*. The solution was to delete the firewall rule in windows and then recreate it, and/or restart the server. *If you check your dashboard, you may find that the server is reporting that the local IP is the localhost, 127.0.0.1. If you run a client on the server machine, it works, but of course any client elsewhere on the network trying to connect to 127.0.0.1 is trying to connect to it's own localhost. Don't forget you can still skip and login in manually with emby for WMC. 1
Tonos 6 Posted April 3, 2015 Author Posted April 3, 2015 Thanks guys - managed to solve it. After deselecting 'Attempt to Wake' in the advanced settings on the Emby Classic client, it now happily logs in. It was like the client was not even trying to log in if it couldnt or didnt need to wake the server. Not sure why all of a sudden it was an issue. Ahh now back to some viewing pleasure. Keep up the good work folks! -Anthony 1
ebr 16173 Posted April 3, 2015 Posted April 3, 2015 That sounds very coincidental as that option should not have affected log on at all. Can you turn it back on and reproduce the problem?
Tonos 6 Posted April 4, 2015 Author Posted April 4, 2015 Right you are.. to reproduce the problem I had to set the Emby client to find server Automatically. Seems that it cant find my server without me specifying it anymore. Probably my network, not sure though! -Anthony
ebr 16173 Posted April 4, 2015 Posted April 4, 2015 Make sure UDP is allowed. Sounds like the firewall is blocking UDP traffic.
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