#TMDB exception - en language invalid

1 messages · Page 1 of 1 (latest)

fiery trellisBOT
#

📝 If you want to review this again, grandmaster.shifu:
: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> 📝

#

Welcome @lilac pewter!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

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.

fiery trellisBOT
#

I've been getting this exception from last 3-4 days. TMDb Error: Language: en is invalid see Configuration.languages and Configuration.primary_translations for the options.

Tried using en-US, removing language param but nothing works.

Attached config and logs.

queen tiger
#

same here

languid dove
#

I can't reproduce this

#

can you do a run with -lr instead of --trace and post that?

--run -lr

#

also fyi the True in --trace True doesn't do anything, you just need --trace

lilac pewter
#

with --run -lr

languid dove
#

ty

#

Ah I think I see the issue, leave it with me I need to speak to one of the team members

lilac pewter
#

Thanks. I was using kometateam/kometa:latest

chilly lagoon
#

try and run again

#

the ssl certs for the translation website I host for kometa expired and didnt auto renew

#

I just renewed them and the site is accessible again

languid dove
chilly lagoon
#

apologies for that too. I added ssl expiry notifications to my uptime kuma container for the translations site so if it doesnt auto renew in february, itll alert my phone

lilac pewter
#

I still see the same error. Do I need to delete some cache or soemthing else?

#

Tried now with --run -lr --no-verify-ssl still fails

chilly lagoon
#

if this is tmdb language @languid dove i dont think that has anything to do with weblate

lilac pewter
#

I think the issue is maybe TMDB isn't returning anything for translations key in response

{'images': {'base_url': 'http://image.tmdb.org/t/p/', 'secure_base_url': 'https://image.tmdb.org/t/p/', 'backdrop_sizes': ['w300', 'w780', 'w1280', 'original'], 'logo_sizes': ['w45', 'w92', 'w154', 'w185', 'w300', 'w500', 'original'], 'poster_sizes': ['w92', 'w154', 'w185', 'w342', 'w500', 'w780', 'original'], 'profile_sizes': ['w45', 'w185', 'h632', 'original'], 'still_sizes': ['w92', 'w185', 'w300', 'original']}, 'change_keys': ['adult', 'air_date', 'also_known_as', 'alternative_titles', 'biography', 'birthday', 'budget', 'cast', 'certifications', 'character_names', 'created_by', 'crew', 'deathday', 'episode', 'episode_number', 'episode_run_time', 'freebase_id', 'freebase_mid', 'general', 'genres', 'guest_stars', 'homepage', 'images', 'imdb_id', 'languages', 'name', 'network', 'origin_country', 'original_name', 'original_title', 'overview', 'parts', 'place_of_birth', 'plot_keywords', 'production_code', 'production_companies', 'production_countries', 'releases', 'revenue', 'runtime', 'season', 'season_number', 'season_regular', 'spoken_languages', 'status', 'tagline', 'title', 'translations', 'tvdb_id', 'tvrage_id', 'type', 'video', 'videos']}```
chilly lagoon
#

this is likely something tmdb changed and @paper lance would likely need to be involved

lilac pewter
#

but interesting thing is if I run through curl it shows returns translations curl -X GET "https://api.themoviedb.org/3/configuration?api_key=key&append_to_response=countries,jobs,languages,primary_translations,timezones

languid dove
#

I don't see why I'm not getting the error though

#

If TMDb changed something I would think it would be consistent

#

I went to master to make sure I was on the same version, installed the requirements to make sure those were the same too

chilly lagoon
#

the translations site has nothing to do with tmdb though

lilac pewter
#

@languid dove with -lr do you see translations coming in your response from tmdb?

languid dove
#

I know, it was just something else to rule out as I noticed it was down

lilac pewter
#

ok, I see it's coming up for you. But for me TMDB response doesn't have that key

#

It has that key, but empty

languid dove
#

Try getting a new api key?

chilly lagoon
#

the only difference in my config is I have region set to US

languid dove
#

I have it set to en

chilly lagoon
#

but im not seeing the issue either in my logs

languid dove
#

I don't have region set

chilly lagoon
#

or language?

languid dove
chilly lagoon
# 
[2024-11-18 18:55:48,214] [config.py:193]             [DEBUG]    | tmdb:                                                                                              |
[2024-11-18 18:55:48,214] [config.py:193]             [DEBUG]    |   apikey: (redacted)                                                                               |
[2024-11-18 18:55:48,214] [config.py:193]             [DEBUG]    |   language: en                                                                                     |
[2024-11-18 18:55:48,214] [config.py:193]             [DEBUG]    |   cache_expiration: 60                                                                             |
[2024-11-18 18:55:48,214] [config.py:193]             [DEBUG]    |   region: US
fiery trellisBOT
#

I C&P'd directly from OP's log:

tmdb:
  apikey: (redacted by Luma)
    #language: en-US
  cache_expiration: 60
    #region:
  language: en
  region:
languid dove
#

😄

chilly lagoon
#

its probably a cache thing?

languid dove
#

Maybe

lilac pewter
#

regenerating API key worked

languid dove
#

Could potentially be cache as anon stated

#

If the API key has changed that would probably force Kometa to ditch the previous cached info and fetch it again

#

Idk why the reponse wouldn't include the language stuff in the first place though, maybe TMDb had a blip

lilac pewter
#

It was only happening with kometa

#

with curl the tmdb api response had language

languid dove
languid dove
#

At some point TMDb gave Kometa a response with no language info

lilac pewter
#

Ah okay. Where is the cache stored? I can delete it any try

languid dove
#

Kometa caches a lot of info to reduce network calls, this is maybe one of them - there may be an action to not cache that info

languid dove
queen tiger
#

Yep deleting that cache worked

#

thanks

slim summitBOT
#

antwanchild used !aenh

@lilac pewter, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.