📝 If you want to review this again, akumara:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
#Does IMDB not work at all even with nightly build? I've spent hours trying different configs
rugged plankBOT
Welcome @snow ingot!
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
rugged plankBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
somber coyote
@snow ingot can you post those attachments again?
snow ingot
Ths is the error.
I did some ping/curl testing and got a Status Code: 202
Content Length: 0 in a return, so its not making me believe that imdb is blocking my data, im running on unraid.
Can you let me know what you need from me to help me troubleshoot? @somber coyote
snow ingot
IMDb Test Collections for Movies
Using correct syntax for latest Kometa nightly build
collections:
IMDb Top 250 - Using imdb_chart (most reliable method)
IMDb Top 250:
imdb_chart: top_movies
collection_order: custom
collection_mode: hide
sync_mode: sync
summary: "The top 250 movies as rated by IMDb users."
sort_title: "!01_IMDb Top 250"
visible_library: true
visible_home: true
visible_shared: true
cache_builders: 12 # Cache for 12 hours
IMDb Bottom 100 - Using imdb_chart
IMDb Bottom 100:
imdb_chart: lowest_rated
collection_order: custom
collection_mode: hide
sync_mode: sync
summary: "The lowest rated movies on IMDb with at least 10,000 votes."
sort_title: "!02_IMDb Bottom 100"
visible_library: true
visible_home: true
visible_shared: true
cache_builders: 12 # Cache for 12 hours
IMDb Popular - Using imdb_chart
IMDb Popular Movies:
imdb_chart: popular_movies
collection_order: custom
collection_mode: hide
sync_mode: sync
summary: "Movies trending on IMDb based on current popularity."
sort_title: "!03_IMDb Popular"
visible_library: true
visible_home: true
visible_shared: true
cache_builders: 12 # Cache for 12 hours
Alternative: IMDb Popular using MDBList (backup method if chart fails)
IMDb Popular (MDBList):
mdblist_list: https://mdblist.com/lists/k0meta/imdb-popular-movies
collection_order: custom
collection_mode: hide
sync_mode: sync
summary: "Popular movies on IMDb via MDBList."
sort_title: "!03_IMDb Popular Alt"
visible_library: true
visible_home: true
visible_shared: true
I ran some python script to test the connection
rugged plankBOT
snow ingot
Do you mind giving me 1 of your imdb collection configs, and ill test it out. Unless its definitely not that?
I dunno im pulling out my hair, been on this for days already
HTTP/2 202
server: CloudFront
date: Fri, 25 Jul 2025 08:31:50 GMT
content-length: 0
x-amzn-waf-action: challenge
cache-control: no-store, max-age=0
content-type: text/html; charset=UTF-8
access-control-allow-origin: *
access-control-max-age: 86400
access-control-allow-methods: OPTIONS,GET,POST
access-control-allow-headers: x-amzn-waf-action
x-cache: Error from cloudfront
via: 1.1 27edb89c2cf32c1ff633bbd43e972ac6.cloudfront.net (CloudFront)
x-amz-cf-pop: SGN50-P1
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: BRrjz8EMXAuAxJKBCQUKrjQt2XhXrqWBQ4ju66RQw_86rYRM5UF0Pw==EditAh,
this is the result from this command in unraid
From Unraid terminal (not Kometa container)
curl -I https://www.imdb.com/chart/top/
I think im gonna give up as it seems im blocked at an IP level somehow, ill just use alternative mdblist options.
But it may be worth noting this for other people who may have been blocked. Cant find any documentation on how to actually troubleshoot the connection first.
somber coyote
It's 830 in the morning; I'll take a look in the next little bit.
IMDb works fine with one issue that is addressed in the nightly branch.
This may be due to using AI, which I have never seen produce any working configs for Kometa.
left island
## IMDb Test Collections for Movies
## Using correct syntax for latest Kometa ni...
your cache_buiders: 12 is 12 days and not 12 hours
snow ingot
would that cause the empty document error?
somber coyote
Well, first, you can leverage the IMDB defaults for these three collections.
But let me give these definitions of yours a try.
snow ingot
can you give me a basic imdb.yml file with the 3 defaults. Ill run it with just that and post the results
somber coyote
In your config:
libraries:
Movies:
collection_files:
- default: imdb
But if
curl -I https://www.imdb.com/chart/top/
is producing an error, then whatever is getting in the way is not part of Kometa and probably the defaults fail the same way.
snow ingot
thats what i thought.
But i dont know what i could have done to get blocked. I have had imdb collections work in the past.
somber coyote
Your YAML works fine for me here in Minnesota, so it appears to be some network issue between you and IMDb.
| Title | + | = | - | Run Time | Status
|======================|=======|=======|=======|==========|=============================
| IMDb Top 250 | 63 | 0 | 0 | 0:00:18 | Created and Updated Metadata
| IMDb Bottom 100 | 48 | 0 | 0 | 0:00:05 | Created and Updated Metadata
| IMDb Popular Movies | 26 | 0 | 0 | 0:00:05 | Created and Updated Metadata
the site loads in my browser fine as well. But it seems the command in kometa gets a cloudfront issue
should this be true?
somber coyote
Does it load via curl from the machine with the browser?
If you run Kometa on the machine with the browser, does it work?
If it's just the UNRaid machine that shows the problem, then that narrows it down to something peculiar to your UNraid environment.
somber coyote
should this be true?
That depends on your network setup. This error doesn't seem related to that.
snow ingot
Nope still and error with unraid console.
somber coyote
Is the browser that loads the site correctly running on the unraid machine?
snow ingot
no its my windows laptop. I have a firefox browser in unraid, let me try that
somber coyote
What if you run the curl command on your laptop?
Next, what happens if you run Kometa on your laptop?
snow ingot
I dont know ive never tried to run kometa on my laptop. Id rather not but i can try for troubleshooting sake if its the last option
the site loads in the firefox-docker container
somber coyote
Well, the thing is that this error is not related to any code that Kometa controls. Kometa is making a boring network request, the same one that every instance of Kometa makes in this instance. So the issue is outside Kometa, apparently in some networking detail.
The curl command failing both from the UNRaid terminal and the Kometa container indicates to me anyway that Kometa code or container config is not implicated.
snow ingot
i did the curl on the m.imdb site and it worked fine. Anyway to change kometa defaults to use that?
somber coyote
Every machine I have access to returns this same thing from the curl command:
$ curl -I https://www.imdb.com/chart/top/
HTTP/2 403
content-type: text/html
server: Server
date: Fri, 25 Jul 2025 14:35:23 GMT
vary: Content-Type,Accept-Encoding,User-Agent
x-amz-rid: 15WWAXBFEVAR096S5FYJ
strict-transport-security: max-age=47474747; includeSubDomains; preload
x-cache: Error from cloudfront
via: 1.1 971cad87e8cdac9c4a5f2f575e735184.cloudfront.net (CloudFront)
x-amz-cf-pop: SFO53-P1
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: OxId1bjLr6yw6wl6Jg-CblfTlgnoGd5VijQDAPzOyMpr25YzWOUulw==
That my Mac laptop, an ubuntu machine in my basement, and an ubuntu server in LA.
somber coyote
i did the curl on the m.imdb site and it worked fine. Anyway to change kometa de...
There is no settings-based way, no.
That quite possibly wouldn't work since Kometa parses the HTML page and presumably the mobile HTML will differ.
snow ingot
Hmm - yea, its annoying but i dont mind using workarounds like tmdb/trakt mirrors.
The last thing is, im in vietnam. Is there any georestrictions there?
somber coyote
The last thing is, im in vietnam. Is there any georestrictions there?
Not on the Kometa side.
Perhaps IMDB has made some change that has only been rolled out to your geographic area.
snow ingot
Hmm possibly.
We could test it by turning on a vpn on one of your kometa-machines to vietnam and running it possibly?
I just wanna know what the damn issue is
but then again its probably a datacenter ip and the amazon-waf will block it regardless? i dunno
Anyhow its late for me. I really apprecaite the thorough troubleshooting! Will work on some alternatives for the imdb collections myself
somber coyote
I don't have access to a VPN with a vietnam exit, so can't try it here.
acoustic patrolBOT
antwanchild used !afnh
@snow ingot, anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.