#Unable to update posters after initial import

1 messages ยท Page 1 of 1 (latest)

robust hingeBOT
#

Welcome @bleak scroll!

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.

lone wigeon
#

Please provide a log.

bleak scroll
robust hingeBOT
#

๐Ÿ“ If you want to review this again, mrfatad:
: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> ๐Ÿ“

#
**Rec 01** - โš ๏ธ๐Ÿ–ฅ๏ธ **LINUXSERVER IMAGE DETECTED**

โš ๏ธ๐Ÿ–ฅ๏ธ LINUXSERVER IMAGE DETECTED
You are not using the official Kometa container image.
In the Kometa discord thread, type !lsio for more information.
For more information on this, [https://kometa.wiki/en/latest/kometa/install/images/?h=linuxserver#linuxserver]
1 line(s) with LINUXSERVER IMAGE issues. Line number(s): 10

robust hingeBOT
#

๐Ÿ“ If you want to review this again, mrfatad:
: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> ๐Ÿ“

bleak scroll
robust hingeBOT
#

๐Ÿ“ If you want to review this again, mrfatad:
: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> ๐Ÿ“

#
**User Info**

Author of Linked Message: MrFatad
Person who Invoked the Command: MrFatad
File Name: meta.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 - โš ๏ธ [WARNING]
Page 08: Rec 02 - ๐Ÿ’ฌ Kometa CACHE
Page 09: Rec 03 - ๐Ÿ’ฌ๐Ÿ’ก๏ธ PLEX DB CACHE ADVICE

fallow mistBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ยฏ_(ใƒ„)_/ยฏ

Log file too big? USE PASTEBIN or ZIP THE FILE

robust hingeBOT
#

๐Ÿ“ If you want to review this again, mrfatad:
: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> ๐Ÿ“

bleak scroll
robust hingeBOT
#

๐Ÿ“ If you want to review this again, mrfatad:
: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> ๐Ÿ“