Treecrusher 5 Posted June 24, 2017 Posted June 24, 2017 Hi everybody, I have recently upgraded my home server to Windows Server 2016. I migrated my Emby server over without any issues; my existing library, watched status etc. all worked without a hitch. I am having a problem adding new titles properly though. The library scan takes hours to complete and it doesn't properly fetch metadata and imagery for new titles. Could somebody please help point me in the right direction to getting this resolved. My latest log is attached. It has lots of errors, but I do not understand how to fix them. One that appears odd to me is that it is trying to contact my default gateway (192.168.1.1). My Emby server is set up on ip 192.168.1.3. Any help will be greatly appreciated. Thanks.server-63633859200.txt
Luke 42080 Posted June 24, 2017 Posted June 24, 2017 @@Treecrusher, it appears the server doesn't have an active internet connection. all outgoing http requests are timing out and failing, everything from tvdb to omdb and moviedb, all of them the same. So it sounds like you need to configure the network connection on the server. let us know if this helps. thanks.
Treecrusher 5 Posted June 25, 2017 Author Posted June 25, 2017 @@Treecrusher, it appears the server doesn't have an active internet connection. all outgoing http requests are timing out and failing, everything from tvdb to omdb and moviedb, all of them the same. So it sounds like you need to configure the network connection on the server. let us know if this helps. thanks. That is helpful thank you. Although I am not sure why Emby doesn't have access to the internet. The server definitely has an internet connection and I have exceptions in windows firewall for the emby server application and for TCP and UDP connections over the 8096 port. When I copy one of the links out of the log (such as: https://www.thetvdb.com/api/B89CE93890E9419B/series/266189/all/en.zip)and paste it into a browser it downloads fine, but for some reason not through Emby. Any thoughts? Thanks again.
ebr 16185 Posted June 25, 2017 Posted June 25, 2017 Your firewall or other security software is blocking the server.
Luke 42080 Posted June 25, 2017 Posted June 25, 2017 Blocking Emby Server is what he means. @@Treecrusher please let us know if this helps. Thanks !
Treecrusher 5 Posted June 26, 2017 Author Posted June 26, 2017 Your firewall or other security software is blocking the server. Blocking Emby Server is what he means. @@Treecrusher please let us know if this helps. Thanks ! At least I know where the root of the problem is. I've had a few weird issues with Server 2016 that I've to resolve. It must be some policy as I turned the firewall off completely and still had the same issue. I will keep on investigating and come back with a solution once I figure it out. Thanks again for your help.
Luke 42080 Posted June 26, 2017 Posted June 26, 2017 @@Treecrusher Thanks for the feedback. Once you've resolved it, please let us know what the answer was. Thanks !
Treecrusher 5 Posted June 28, 2017 Author Posted June 28, 2017 I'm struggling with this issue. I've completely turned the firewall off and I still get the same issue. I've added Emby to the list of trusted apps with no change, I've tried running Emby as administrator with no change and also logged in as administrator and run Emby directly from the admin account, still with no change. Does anybody have any thoughts on why/how Windows Server 2016 would be stopping Emby from accessing the internet? I ran Windows Server 2008 for years with no issues, but 2016 seems to have these tricky little issues that are almost beyond me to resolve. I would really appreciate any kind of thoughts or hints as to what might be the issue as I am out of ideas. Thanks again for your support.
Happy2Play 9782 Posted June 28, 2017 Posted June 28, 2017 I'm struggling with this issue. I've completely turned the firewall off and I still get the same issue. I've added Emby to the list of trusted apps with no change, I've tried running Emby as administrator with no change and also logged in as administrator and run Emby directly from the admin account, still with no change. Does anybody have any thoughts on why/how Windows Server 2016 would be stopping Emby from accessing the internet? I ran Windows Server 2008 for years with no issues, but 2016 seems to have these tricky little issues that are almost beyond me to resolve. I would really appreciate any kind of thoughts or hints as to what might be the issue as I am out of ideas. Thanks again for your support. Could it possibly be IE ESC?
rhodges 49 Posted June 28, 2017 Posted June 28, 2017 I am running Emby on a Windows 2016 server. I don't remember doing anything special to get it to work. Can you access Emby on other computers in your network? Double check the setting that lets you bind to a specific ip address. You mentioned you copied the links out of the logs and tried them in the browser. What browser did you try them in? IE? If not, try them in IE, see what that does. Do you have more than 1 network adapter or maybe Hyper-V installed? There could be issues around that. I've tripped myself up there a few times. Any anti-virus or anything like that? Is the server running as a guest of another VM? Does VM host have virus scan software? You might check your router's firewall/logs. I've heard of some aggressive ones that will block outbound connections sometimes if things such as user agents are not sent in the request. I'm going out on a limb with that suggestion. Try doing a telnet (with correct port) to one of the urls. If it connects, then something else is in play.
Luke 42080 Posted June 28, 2017 Posted June 28, 2017 @@Treecrusher are the same errors still showing up in your server log?
Treecrusher 5 Posted June 29, 2017 Author Posted June 29, 2017 Could it possibly be IE ESC? I am running Emby on a Windows 2016 server. I don't remember doing anything special to get it to work. Can you access Emby on other computers in your network? Double check the setting that lets you bind to a specific ip address. You mentioned you copied the links out of the logs and tried them in the browser. What browser did you try them in? IE? If not, try them in IE, see what that does. Do you have more than 1 network adapter or maybe Hyper-V installed? There could be issues around that. I've tripped myself up there a few times. Any anti-virus or anything like that? Is the server running as a guest of another VM? Does VM host have virus scan software? You might check your router's firewall/logs. I've heard of some aggressive ones that will block outbound connections sometimes if things such as user agents are not sent in the request. I'm going out on a limb with that suggestion. Try doing a telnet (with correct port) to one of the urls. If it connects, then something else is in play. @@Treecrusher are the same errors still showing up in your server log? Thanks for all your help, I've made progress. I installed Chrome when I first built the machine and it has no problems connecting to the outside world. But IE doesn't connect to any of the websites Emby is trying to connect to. Not sure how to make telnet connect to those websites (tried but couldn't get it to work on my main machine either) but I tried tracert and it just times out on any website. So looks like IE might have something to do with it. The errors are still the same. Although there are so many of them and I haven't directly compared to confirm whether they are exactly the same. I will work on getting the links working in IE and see how that goes. Thanks again.
Happy2Play 9782 Posted June 29, 2017 Posted June 29, 2017 Thanks for all your help, I've made progress. I installed Chrome when I first built the machine and it has no problems connecting to the outside world. But IE doesn't connect to any of the websites Emby is trying to connect to. Not sure how to make telnet connect to those websites (tried but couldn't get it to work on my main machine either) but I tried tracert and it just times out on any website. So looks like IE might have something to do with it. The errors are still the same. Although there are so many of them and I haven't directly compared to confirm whether they are exactly the same. I will work on getting the links working in IE and see how that goes. Thanks again. I would test disabling IE ESC to see if it resolves your issue. If it does and want IE ESC enabled you will need to look a adding sites to the trusted list.
Treecrusher 5 Posted June 29, 2017 Author Posted June 29, 2017 I would test disabling IE ESC to see if it resolves your issue. If it does and want IE ESC enabled you will need to look a adding sites to the trusted list. I have IE ESC disabled, windows firewall disabled and logged in as admin. In Chrome everything works perfectly. In IE some websites work, others don't. In command line I can ping and tracert and nslookup some ips but then it times out on others. Interestingly it times out on some ip addresses that work in IE. Clearly not an Emby problem, so I appreciate the help.
rhodges 49 Posted June 29, 2017 Posted June 29, 2017 Do you have some sort of proxy server or proxy server settings specified in IE? I don't remember if those settings flow down to .NET applications or not. Chrome might work because it might not be using the system-wide proxy settings. Double check that you have the firewall properly disabled. It can be disabled for Public/Private and different classes of connections. Your network adapter may say it is a Public connection (more of a classification) and you only disabled the firewall for Private connections. I would expect there to be some sort of log somewhere if the firewall is blocking it. Double check the logs. ping/tracert are ICMP traffic types and those packets have been abused over the years and thus can get dropped often in order to not bog down networks. Regarding telnet, you might have to install the feature for a telnet client. I don't remember on windows server, how, but a search should show you. Once installed, do something like: for https://www.google.com open a command prompt and type: telnet www.google.com 443 Note: If the url is http:// then use 80 and not 443. If it immediately goes to a black screen, then the connection happened. If it times out, then you have other network problems. Those can be anything from bad cabling to ISP problems.
Treecrusher 5 Posted June 30, 2017 Author Posted June 30, 2017 Do you have some sort of proxy server or proxy server settings specified in IE? I don't remember if those settings flow down to .NET applications or not. Chrome might work because it might not be using the system-wide proxy settings. Double check that you have the firewall properly disabled. It can be disabled for Public/Private and different classes of connections. Your network adapter may say it is a Public connection (more of a classification) and you only disabled the firewall for Private connections. I would expect there to be some sort of log somewhere if the firewall is blocking it. Double check the logs. ping/tracert are ICMP traffic types and those packets have been abused over the years and thus can get dropped often in order to not bog down networks. Regarding telnet, you might have to install the feature for a telnet client. I don't remember on windows server, how, but a search should show you. Once installed, do something like: for https://www.google.com open a command prompt and type: telnet www.google.com 443 Note: If the url is http:// then use 80 and not 443. If it immediately goes to a black screen, then the connection happened. If it times out, then you have other network problems. Those can be anything from bad cabling to ISP problems I don't have any special proxies and my router isn't blocking anything. I have been disabling all firewalls when testing; public, private and domain (the connection is DOMAIN.Local, and this is something I can't change). I installed the OS using default settings, turned off IE ESC and installed Chrome. Chrome doesn't have any issues, but clearly IE etc. is being blocked by something. I've looked at the windows firewall log files but there is nothing in there. I have other machines on the same network, they're all running win 10 so am able to test things outside the server 2016 environment. Ping, tracert etc. all work on the other machines, just not the server machine. I installed the telnet feature, I just couldn't work out the syntax (I was typing telnet, pressing enter and then trying to type the URL), so thanks for the heads up on that. When I telnet www.thetvdb.com on one of my win 10 machines it connects instantly, but on the server it sits for around a minute with "Connecting to www.thetvdb.com..." and then it just times out. trying to connect to www.google.com on 443 gets a similar result. I am very close to ditching server 2016 and just installing win 10 on that machine. Only thing keeping me in is that I purchased a server 2016 licence and don't want it to go to waste. Again, I appreciate everyone's brainstorming on the issue; It is really helpful. I only have an hour or so each night to look at it between family stuff and work etc. hence the time between responses. Thanks again.
rhodges 49 Posted June 30, 2017 Posted June 30, 2017 I don't really know then. Proxy and windows firewall/router firewall settings are the only things I can think of. Longshot...You might double check your DNS server. A wild guess, but maybe they aren't resolving properly on the 2016 box and maybe Chrome will fall back internally to their 8.8.8.8 DNS servers. IPCONFIG /ALL and double check your DNS Servers and Default Gateway. A "telnet www.thetvdb.com 80" or "telnet www.google.com 443" should connect instantly like you see on your win 10 box. I have attached some pics highlighting what I'm referring to on the firewall. You probably already know this, but, on the off chance something got miss communicated... I am out of ideas at this point. Like I mentioned, I have Windows 2016 up and running and encountered none of these issues. Maybe just blow away the install and start again? Install and then try the telnet/IE thing right out of the box. Keep trying that after any post install configuration step you do.
Solution Treecrusher 5 Posted July 1, 2017 Author Solution Posted July 1, 2017 Ok, it is fixed! The clue was definitely the DNS server settings, although this wasn't the actual cause. My network type was DOMAIN.Local, which I found was because my server had Active Directory Domain Services installed and running. It seems this service was somehow affecting connections (I'm not entirely sure how). For some reason this didn't effect Chrome, but did effect IE, the console and .net. Long story short I removed all Active Directory services from my server and everything is running as it should. Thank you again for everybody's help! I would of given up long ago without the hints on things to look in to. 1
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