Dr Herbalist 0 Posted April 25, 2022 Posted April 25, 2022 Emby server suddenly seems to have an issue retrieving metadata from api.themoviedb.org. It looks as though it's getting a "connection refused" error. I've tried with different IP addresses in different regions and still receive the same message. I'm wondering if perhaps the API key has expired? I can't seem to find in the Emby server settings where I might go about adding a new API key for this service. Please see the attached logs. Thanks. embyerror.txt
Luke 42085 Posted April 25, 2022 Posted April 25, 2022 Hi, it seems to be working ok from here. Are you still running into this?
Dr Herbalist 0 Posted April 25, 2022 Author Posted April 25, 2022 Hi Luke, Unfortunately I am. Please see the attached logfile. Is every Emby customer using the same API key, or is it a different one per customer? Many thanks, Herb embyerror2.txt
Happy2Play 9783 Posted April 25, 2022 Posted April 25, 2022 2 minutes ago, Dr Herbalist said: Hi Luke, Unfortunately I am. Please see the attached logfile. Is every Emby customer using the same API key, or is it a different one per customer? Many thanks, Herb embyerror2.txt 4.89 kB · 0 downloads The project uses the same key. Not seeing a issue here either. Are you able to open the urls from the log in a browser?
Dr Herbalist 0 Posted April 25, 2022 Author Posted April 25, 2022 The plot thickens. I can send a request to the API from a browser and get a response. It first refused the connection but after refreshing it a few times it returned the data. When I send the request from powershell without a useragent I get a refused connection, no matter how many times I send the request. Could it be a problem with the useragent? The particular IP address the network interface uses here is registered to Lithuania (so shouldn't be getting caught up with the Russian "special conflict"). Any other ideas?
Luke 42085 Posted April 25, 2022 Posted April 25, 2022 You may have something on your end preventing Emby Server from sending the outgoing request, such as firewall, security software, or VPN. Those are the most common causes that we see of this.
Dr Herbalist 0 Posted April 25, 2022 Author Posted April 25, 2022 (edited) I guess the fact the API isn't responding outside of Emby too would indicate that it's not an Emby issue at least, so It's good that we have ruled that out. I wish I could get logs from themoviedb.org server and see why the request is being dropped. I wonder if they have a WAF or something in place that doesn't like my traffic. theTVdb.com seems to work fine. All other outbound API calls to various other services are working correctly... Weird. Edited April 25, 2022 by Dr Herbalist
Solution Dr Herbalist 0 Posted May 13, 2022 Author Solution Posted May 13, 2022 (edited) Hey. Just thought would let you know that I managed to get to the bottom of it. It turns out that DNS lookups to api.themoviedb.org were returning 127.0.0.1 as the server address. No idea why this is happening using Google DNS servers or CloudFlare. I ended up using Quad9 for DNS resolution and it now returns the correct addresses. This might explain why it worked in a Chrome browser but not within the OS. I imagine Chrome has its own DNS cache or alternate method of lookup as a fall-back. It's odd because it's not a host record or anything overriding it, when I switched out DNS servers lookup is working. Either way, thanks your your time looking into the issue. It's all working as it should now. Edited May 13, 2022 by Dr Herbalist
Happy2Play 9783 Posted May 13, 2022 Posted May 13, 2022 Interesting as I cannot replicate that test. Spoiler PS C:\Users\Media> nslookup api.themoviedb.org 1.1.1.1 Server: one.one.one.one Address: 1.1.1.1 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:fa00:c:174a:c400:93a1 2600:9000:20be:fc00:c:174a:c400:93a1 2600:9000:20be:2c00:c:174a:c400:93a1 2600:9000:20be:4800:c:174a:c400:93a1 2600:9000:20be:bc00:c:174a:c400:93a1 2600:9000:20be:400:c:174a:c400:93a1 2600:9000:20be:2000:c:174a:c400:93a1 2600:9000:20be:d000:c:174a:c400:93a1 52.84.162.18 52.84.162.76 52.84.162.22 52.84.162.78 PS C:\Users\Media> nslookup api.themoviedb.org 8.8.8.8 Server: dns.google Address: 8.8.8.8 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:d400:c:174a:c400:93a1 2600:9000:20be:be00:c:174a:c400:93a1 2600:9000:20be:5200:c:174a:c400:93a1 2600:9000:20be:7800:c:174a:c400:93a1 2600:9000:20be:dc00:c:174a:c400:93a1 2600:9000:20be:4e00:c:174a:c400:93a1 2600:9000:20be:5e00:c:174a:c400:93a1 2600:9000:20be:9a00:c:174a:c400:93a1 52.84.162.78 52.84.162.76 52.84.162.22 52.84.162.18 PS C:\Users\Media> nslookup api.themoviedb.org 9.9.9.9 Server: dns9.quad9.net Address: 9.9.9.9 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:3c00:c:174a:c400:93a1 2600:9000:20be:dc00:c:174a:c400:93a1 2600:9000:20be:6200:c:174a:c400:93a1 2600:9000:20be:4e00:c:174a:c400:93a1 2600:9000:20be:de00:c:174a:c400:93a1 2600:9000:20be:4a00:c:174a:c400:93a1 2600:9000:20be:3800:c:174a:c400:93a1 2600:9000:20be:1c00:c:174a:c400:93a1 52.84.162.76 52.84.162.22 52.84.162.18 52.84.162.78
Dr Herbalist 0 Posted May 18, 2022 Author Posted May 18, 2022 On 13/05/2022 at 21:05, Happy2Play said: Interesting as I cannot replicate that test. Reveal hidden contents PS C:\Users\Media> nslookup api.themoviedb.org 1.1.1.1 Server: one.one.one.one Address: 1.1.1.1 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:fa00:c:174a:c400:93a1 2600:9000:20be:fc00:c:174a:c400:93a1 2600:9000:20be:2c00:c:174a:c400:93a1 2600:9000:20be:4800:c:174a:c400:93a1 2600:9000:20be:bc00:c:174a:c400:93a1 2600:9000:20be:400:c:174a:c400:93a1 2600:9000:20be:2000:c:174a:c400:93a1 2600:9000:20be:d000:c:174a:c400:93a1 52.84.162.18 52.84.162.76 52.84.162.22 52.84.162.78 PS C:\Users\Media> nslookup api.themoviedb.org 8.8.8.8 Server: dns.google Address: 8.8.8.8 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:d400:c:174a:c400:93a1 2600:9000:20be:be00:c:174a:c400:93a1 2600:9000:20be:5200:c:174a:c400:93a1 2600:9000:20be:7800:c:174a:c400:93a1 2600:9000:20be:dc00:c:174a:c400:93a1 2600:9000:20be:4e00:c:174a:c400:93a1 2600:9000:20be:5e00:c:174a:c400:93a1 2600:9000:20be:9a00:c:174a:c400:93a1 52.84.162.78 52.84.162.76 52.84.162.22 52.84.162.18 PS C:\Users\Media> nslookup api.themoviedb.org 9.9.9.9 Server: dns9.quad9.net Address: 9.9.9.9 Non-authoritative answer: Name: api.themoviedb.org Addresses: 2600:9000:20be:3c00:c:174a:c400:93a1 2600:9000:20be:dc00:c:174a:c400:93a1 2600:9000:20be:6200:c:174a:c400:93a1 2600:9000:20be:4e00:c:174a:c400:93a1 2600:9000:20be:de00:c:174a:c400:93a1 2600:9000:20be:4a00:c:174a:c400:93a1 2600:9000:20be:3800:c:174a:c400:93a1 2600:9000:20be:1c00:c:174a:c400:93a1 52.84.162.76 52.84.162.22 52.84.162.18 52.84.162.78 It probably has to do with my DNS lookup originating for a Russian IP address.
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