trouble with guide data after restoring on new server from backup

[zape 2]

After moving my Emby server from a dead box, over to a new one (yay backups), I noticed my guide data no longer works properly.  If I click on one of the existing data points, or try to create a new one I get this message:

There was an error downloading tv lineups. Please ensure your information is correct and try again.

I did put in my Emby premier key, and it seems to be working for me elsewhere.

While I do have some older Schedules Direct guides on the system, it won't even let me create a new Emby Guide one.  It errors as soon as I enter the zip code.

Log file attached.

embyserver.txt

[Carlo 4330]

Hi, your log file is very "noisy" with errors due to it trying to automatically port map which isn't working (router settings).
Please turn off auto port mapping in the network menu.

Emby is having trouble "No such host is known" trying to communicate out to our guide provider.
 

Please change the network setting above then restart Emby server and try the guide update again.
Upload a new server log file after that which should be much easier to read.

Thanks

[zape 2]

I changed it, restarted and see the same error.  new log attached.

embyserver (1).txt

[Carlo 4330]

Your log is showing "No such host is known." for external access to some resources like our EPG guide server.
Here is one failing trying to pull down an image.

https://www.thetvdb.com/banners/v4/episode/8456048/screencap/60dc623b2bba5.jpg

From the windows pc running Emby Server can you open that URL?
 

[zape 2]

yes, I was able to open the URL in both Chrome and Edge from that PC.

[Happy2Play 8252]

34 minutes ago, cayars said:

Your log is showing "No such host is known." for external access to some resources like our EPG guide server.
Here is one failing trying to pull down an image.

https://www.thetvdb.com/banners/v4/episode/8456048/screencap/60dc623b2bba5.jpg

From the windows pc running Emby Server can you open that URL?
 

Don't know why the errors happen but you can see it works a few lines under the errors.

2021-10-01 17:44:57.205 Info HttpClient: GET https://www.thetvdb.com/banners/v4/episode/8456048/screencap/60dc623b2bba5.jpg
2021-10-01 17:44:57.462 Info CoverArt: image enhance of A Yacht in Kneed took 0.051 seconds.
2021-10-01 17:44:57.544 Info Server: http/1.1 Response 200 to 192.168.0.103. Time: 933ms. 

But am guessing the issue is here.

2021-10-01 17:47:13.900 Info Server: http/1.1 GET http://192.168.0.85:8096/emby/LiveTv/ListingProviders/Lineups?Id=75cb3c961f7c4531a231d1605a79730c&Location=35242&Country=USA&Type=embygn&X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox&X-Emby-Device-Id=7d706c4b-7a4c-4c10-8ed5-56927b33d8d6&X-Emby-Client-Version=4.6.4.0. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0
2021-10-01 17:47:13.987 Info HttpClient: GET https://data.tmsapi.com/v1.1/lineups?country=USA&postalCode=35242
2021-10-01 17:47:14.027 Error HttpClient: Error getting response from https://data.tmsapi.com/v1.1/lineups?country=USA&postalCode=35242
	*** Error Report ***
	Version: 4.6.4.0
	Command line: C:\Users\james\AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp
	Operating system: Microsoft Windows 10.0.19041
	Framework: .NET Core 3.1.13
	OS/Process: x64/x64
	Runtime: C:/Users/james/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	Processor count: 4
	Data path: C:\Users\james\AppData\Roaming\Emby-Server\programdata
	Application path: C:\Users\james\AppData\Roaming\Emby-Server\system
	System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: No such host is known.
	 ---> System.Net.Sockets.SocketException (11001): No such host is known.
	   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
	   --- End of inner exception stack trace ---
	   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
	   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)
	   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
	   at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
	   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
	   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
	   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
	   at System.Net.Http.DiagnosticsHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
	   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
	   at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
	Source: System.Net.Http
	TargetSite: Void MoveNext()
	InnerException: System.Net.Sockets.SocketException: No such host is known.
	Source: System.Private.CoreLib
	TargetSite: Void Throw()
	   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
	
2021-10-01 17:47:14.033 Info Server: http/1.1 Response 500 to 192.168.0.75. Time: 134ms. 

 

[Luke 37028]

Something is preventing your Emby Server from sending out these requests. Typical causes are firewall, security software or VPN. Can you please look into that? Let us know if it helps. Thanks.

[Carlo 4330]

Or some kind of DNS issue based on the "No such host is known" message.

Strange that some requests work and other don't as @Happy2Play mentioned.

@zape if you haven't tried this already reboot your router to see if this helps improve things.
If that doesn't help you could try changing the DNS server entries to 8.8.8.8.

[zape 2]

TL/DR:

Router firmware update created issues with my local DNS.

Full Version:

Thanks Cayars and Luke.  It was, indeed, a DNS issue.  I found that when putting the data.tmsapi.com call into my browser, it initially popped to "site can't be reached", then would resolve and I'd get the unauthorized error.  When I was moving from the dead box, I updated my port forwarding and noticed the router had a security update.  In diagnosing the DNS, I found that pinging the api.tmsapi.com only resolved about once in every 6-7 tries.  Then I found that the Nighthawk X6 R8000 has other posts on the forums of users with DNS issues having problems.  Rolling back to earlier firmware fixed the problem.  I'm sure I would have eventually noticed this in other things too, but the browsers are doing something to keep trying to resolve, and that has been masking the issue.

 

Thanks again for the help, and sorry this was environmental and I brought it here.

[Carlo 4330]

Awesome you got that figured out.  Something like this can drive you crazy!