📝 If you want to review this again, tony_87885:
: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> 📝
#Overlays not populating on Movies or TV Showa
1 messages · Page 1 of 1 (latest)
Welcome @round copper!
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.
I've configured Quickstart to show ratings overlays on Movies and TV Shows (in a test library). Colletions are populating just fine but no overlays whatsoever are showing up. In the yaml, I'm not seeing any code for overlays under either Movies and TV Shows, either.
Full meta.log attached (hopefully this is what you need). Also attaching the yaml generated by Quickstart. Please let me know what else I can provide. Thanks!
**User Info**
Author of Linked Message: Tony
Person who Invoked the Command: Antwan
File Name: meta-2.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - ❌ [ERROR]
Page 08: Rec 02 - ❌ TO BE CONFIGURED ERROR
Page 09: Rec 03 - ⚠️ [WARNING]
Page 10: Rec 04 - 💬 CONVERT WARNING
Page 11: Rec 05 - 💬💡️ PLEX DB CACHE ADVICE
Page 1/11
@round copper The config is in the log so there's no need to provide it separately.
oh! Sorry, figured more info was better than not enough
No worries, just letting you know for the future.
Thank you
There are no overlays defined in that config.
I was seeing that as well, but I’ve enabled them in QuickStart (ratings and studio information , as well as resolution). Where could the discrepancy come from?
I’ve gone back through the settings a few times and nothing seems to populate any overlays in the config
The config in use during the run that generated that log has no overlays defined in it.
Have you regenerated the config after making changes?
I have, a couple of times. The overlays were always turned on from the beginning too. That's my main desire of using this, so I turned them on right away
@floral swift Any idea?
Just redid it now, too. Added a couple of different collections. Those collections populated in the yaml but still no overlays.
Must be some issue in Quickstart.
Oof… so master is broken as well? Fun times
On the last page, where the yaml is generated, can you share the redacted config please?
I have not run master in a while because we have been working on a full overlay editor for the defaults…
@round copper 
Of course! Missed your message yesterday. Here is a redacted config I generated today (with mostly the same settings). Thanks! @floral swift
https://github.com/Kometa-Team/Quickstart/pull/990 will have fixes to QS develop build. Its building now and should be ready within 20 minutes of this message.
Thanks! Attaching a couple files here, it seems like its still not populating any overlay fields.
There were way more options in the overlay section, though! That looked nice
Is there a setting I'm missing in the UI to get this working? Could this be user error?
Making sure you’ve pulled the latest develop… it’s develop not master
There is a little support info button. Please click and copy and paste results here
I see the image he posted is develop. Were you seeing something different?
So things seem pretty normal so far.
Can you go to the libraries page and take a screenshot of maybe a selection of the Video Format overlay within the included movies-test, hit reset to default, then jump to final config and see if the overlays config section shows up.
I didn’t see the screenshot. Lol
And see here how the section is now found in the config
Based on what we get back from Tony, they could try docker or local install to see if problem follows. I cannot repro this behaviour ATM.
Also I just tested on container build:
#==================== docker_unraid ====================#
# docker_unraid config created by Quickstart on 2026-01-12 19:44:32
# System Information
# OS: Linux 6.12.54-Unraid
# Docker: True
# CPU: Unknown CPU (96 cores)
# Memory: 251887 MB / 1547848 MB (16%) | 1295960 MB Free
# Python: 3.13.11
# Git: Unavailable
# Connected to Plex server NZWHS01 version 1.42.2.10156-f737b826c
# Running on Linux version 6.12.54-Unraid
# Plex DB cache setting: 2048 MB
# PlexPass: True on Public update channel.
# Scheduled maintenance running between 2:00 and 5:00
# Quickstart: 0.9.7-build6 | Branch: develop | Environment: Docker
###
# Libraries configured with Quickstart: 1 movie, 1 show
# Information on library: TestMovies
# Type: Movie
# Agent: tv.plex.agents.movie
# Scanner: Plex Movie
# Ratings Source: Rotten Tomatoes
# Content Count: 7 movies
#
# Information on library: TestTV Shows
# Type: Show
# Agent: tv.plex.agents.series
# Scanner: Plex TV Series
# Ratings Source: N/A
# Content Count: 6 shows / 176 episodes
###
I’ll get right on this and report back. Happy to try docker, too. I did local because I read somewhere local gives “more options” but good to know you can’t reproduce it, so it’s something I’m doing
And I see this:
- default: video_format
template_variables:
font: Inter-Medium.ttf
font_size: 55
font_color: '#FFFFFFFF'
back_align: center
back_color: '#00000099'
back_height: 105
back_width: 305
back_line_color: '#00000000'
back_line_width: 1
back_padding: 1
back_radius: 30
horizontal_offset: 15
vertical_offset: 30
I appreciate all the help so far!
You are not actually running local
😅😅
You are running a “frozen” build
In the readme, the local install is I think the 5th option
Ok! I’m relatively new to this and clearly know just enough to get myself in trouble haha
All good
Oh yea 100% did the third option
So 1,2,3 are frozen builds that basically means we attempted to make it a single click install.
4 is container
5 is true “local” install
Open a terminal prompt in your Unix build not sure of version…
git clone https://github.com/Kometa-Team/Quickstart
cd Quickstart
git checkout develop
git stash
git stash clear
git pull
python3 -m venv venv
source venv/bin/activate
python3 -m pip install --upgrade pip
python3 -m pip install -r requirements.txt
And then to run QuickStart:
source venv/bin/activate
python3 quickstart.py
But before that, I would still like to see what is going on with your frozen builds
Just tried the windows frozen build and all good there as well
Yea I am clearly doing something wrong. I'm confirmed running local now, I reset to default all the overlays like you mentioned and the config still looks the same for me. No overlay info anywhere.
Am I supposed to have a folder of all the overlay assets somewhere for it to work?
I'm attaching a few things here to look through...
I'm going wrong somewhere
I'm using the UI on MacOS but I SSH into my Linux machine where I installed both the frozen and local version. I tried in both Safari and Chrome with the same results. No overlay configs anywhere
Based on image, 4 were selected. Can you unselect all collections please
I wonder if that’s somehow getting in the way
All collections unselected and overlays simplified
To answer you question, all QS does is produce a config file. So no need to have the actual images there. That being said we still have a couple of options to review.
So please enable debug logging.
Either through taskbar icon or go into .env and make QS_DEBUG=1
With icon, qs will restart automatically, with .env, please restart qs manually
Then go back to libraries page and select/unselect something and go to next page. Inside the config folder will be a folder called debug_logs there will be two json files for the library page. Please review for any secrets (should not be any) and share them here
Took me a second to find it, the .env file is called ".env.example" would that change anything?
Restarting QS now after changing
Rename to .env
ok
Do you have a gui Unix or is it 100% text
Both, I'm running terminal on Mac OS for SSH but the linux is headless and I'm connected to the GUI via NoMachine (I dont see the taskbar icon, though)
Yeah so that’s likely not what we built the icon to work on but that should be fine…
Was curious more than anything
Dumb moment here, how am I restarting this?
run this again?
source venv/bin/activate
python3 quickstart.py
So the browser you are using is…?
Then walked through it again and got to final validation before checking
Right now I'm doing it in Chrome
Can you have the inspect open to ensure there are no errors popping up there?
That is strange…. The folder should have every page as a json
Like the image I shared… unless of course debug is still off.
Console tab… those are not real errors
I didnt think so
Chrome inspect has a console tab
Click that and as you navigate around you will see a bunch of items show up in the console
Changed it to 1, then did the restart
Can you ls -al the config directory to show me the results please?
blacked out the computer name
Ran the same command in the debug_logs folder and it came back empty
So… where is .env ?
In the quickstart root
You need to save it into the config directory as .env
That’s why you are not in debug yet
The good news is that this support ticket has given me about three new ideas for future support. lol
I forgot that we also added this… lol
Which would have created the .env I believe with the right setting
In any case…
When you start, the messages should show you that debug is enabled…
this is new...
It worked before moving the env file
For fun (this is fun, right), I moved the env file back to the quickstart root and added the --debug command and it started back up
Yeah the .env.example has some extra things in there that are not really needed for our purposes here.
So yeah, starting up in —debug was the way to go. Those debug_logs should be pouring into that folder as you navigate around
Form_data is what is “submitted” from the page and the retrieved is what the page retrieved from the db.
even with the env file in the quickstart root? It wouldnt start after I moved it to config and gave me the error
Hence the request for both json files after you get to the libraries page.
Unfortunately, still no files in the debug logs folder, I've been navigating all around QS
Let’s not worry about that. If you started with —debug, that’s what counts.
This is so peculiar
When you started in —debug, what did the console state? You have a screenshot to share?
Says debug enabled
So it says it’s enabled and yet the folder is still empty. Weird!
Ok… have you ever used any tools to open up SQLite db files before?
I have not
What we are trying to determine is whether the libraries page is committing the overlays to the SQLite db
But am open to it!
If it dos not commit to the db, then on the final page, it won’t pull it from the db
The json files I showed in the windows folder would have helped us determine that.
quickstart.sqlite?
In case your os happens to have more than one process running could you perform a ps -ef|grep quickstart
Yes quickstart.sqlite
But you will need a tool like dbbrowser to open it up. It sure what would work on macOS
****** 837502 826565 0 21:35 pts/2 00:00:04 python3 quickstart.py --debug
****** 846338 846282 0 21:50 pts/1 00:00:00 grep --color=auto quickstart
Ok… so only 1 running
Download and Install:
Visit the DB Browser for SQLite website.
Download the macOS version (either standard installer or Homebrew option).
Install the application like any other macOS app.
Open the application: Launch DB Browser for SQLite.
Open your file:
Click the "Open Database" button.
Navigate to your SQLite file in the Finder window and select it.
Interact with the database: You can now browse data in a spreadsheet-like interface, execute SQL queries using a dedicated tab, and manage tables and indexes visually.
Looks like they have a macOS client
I installed on the Linux for ease of navigating to the client but thank you for providing those steps
I have the sqlite db open
This data?
1 sec please and yes that information… for your config which I think is wizardly_
Right now im on wizardly in Chrome
So click on the libraries blob data for wizardly
The content will be on the right and kind of hard to read… but should contain the overlay settings within that blob data
The challenge is actually being able to read any of that from dbbrowser. Very difficult.
Honestly not sure why debug logs not working… if you look at config/logs/quickstart.log there might be some hints in there
Yes, very challending indeed. SO much text, trying to sort through it but its overwhelming.
The quickstart.log has lots of references to "Loading overlay_config...". Thats the only instance where "overlay" is in the .log file
Man, I wiped all references to Quickstart and started over from scratch. First with the develop build, followed your install exactly and ran it with --debug straight away. Still no debug logs. Terminal is showing me this every time I click around:
[2026-01-13 09:36:32,077] [DEBUG] | [7fc5ec98] Incoming request size: 0.07 KB
[2026-01-13 09:36:39,710] [DEBUG] | [7fc5ec98] Incoming request size: 0.05 KB
[2026-01-13 09:36:39,711] [DEBUG] | [7fc5ec98] Form field count: 2
but nothing in the folder.
Then I removed that instance of Quickstart and installed the local master version, just to test. Ran it straight away with --debug and same thing. No files but terminal is telling me it's debugging.
I'm going to try a docker install just to test.
We might have a bug for the debug_folders on non-windows os. Your docker test should pinpoint this.
Same situation with docker...no overlays anywhere in the config but I'm having a hard time enabling debug in docker
It's confirmed disabled from the logs and I can't seem to enable it
Why dont I try installing this on WIndows to further test? I have a windows machine I can test this on
This is the craziest thing. I followd all install directions for Windows. The bottom of the page confirms I'm on develop, the system tray confirms I have debug enabled.
Just went through it all again and no overlays in the config and no files in the debug_logs folder...
WAIT A MINUTE. I was doing this entirely on the test libraries. I just went through it again on my actual libraries and the yaml has overlay data in it now! I don't know where to go from here haha
What in the world???
No idea how test libraries could be the cause of overlay configs not being written.
We read in the libraries from your plex server in libraries page. As you select things, like collections or overlays for that library, it’s written to the SQLite db. Then on last page we read from db and produce the yml.
When you run kometa on that last page after it’s been updated or installed, that’s the next time that this process interacts with plex.
As for why the debug_logs don’t show up… I am also at a loss as the perms you shared from your directory listing seems fine
On the libraries page, there is a button about halfway down… where you can expand what QuickStart finds on your plex server. When you expand that, does it look complete?
Clicking that will expand a bunch of information about your plex server so maybe that’s somehow affecting quickstart and how it tris to process your overlays… I am really grasping at straws here…
It does
At this point, I feel like my desire to have overlays in my Plex library is going to work once I configure them exactly how I want. This does not at all solve the WHY all of this wasn't working on test libraries but my next question for you is:
What are my next steps? I'll copy/paste the yaml to my actual Kometa config and then everything will populate? Or will I need to download any specific assets/fonts/etc to make the overlays work?
Unless you tell me libraries are missing
So once you are on the final page there are a couple of options…
1- run it there and see the results
2- download the config and place it in your kometa directory so that when Kometa runs, it uses the downloaded config.
The final page gives you guidance on next steps in a modal popup if you click it.
Perfect! Seriously thank you for all the help. We really went down a rabbit hole last night, I appreciate all the time you took trying to figure this out with me.
bullmoose20 used !aenh
@round copper, 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.