Since a few weeks I am unable to create any collections. I stepped into some issues and decided to make a clean install.
Now I am unable to create any collections, even the most basic ones.
I get the error "Collections URL Error "URL Error: No file found at https://raw.githubusercontent.com/Kometa-Team/Translations/master/defaults/en.yml" which I am unable to solve and I am wondering if its related?
That is the only error I get.
#Currently unable to create any collections.
1 messages · Page 1 of 1 (latest)
Welcome @scarlet surge!
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.
📝 If you want to review this again, antwanchild:
: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 02** - ❌⏰ **KOMETA SCHEDULED TIME CONFLICT**
❌⏰ KOMETA SCHEDULED TIME CONFLICT
This Run took: 0:00:51
Time between Kometa Scheduled time and Plex Maintenance start: 20:00:00
Kometa scheduled start time: 5:00
Plex Scheduled Maintenance start time: 3:00
Plex Scheduled Maintenance end time: 7:00
You are within the maintenance window between Plex maintenance start time: 3:00 and end time: 7:00. Adjust the Kometa Scheduled start time to 7:00 or adjust the Plex Scheduled Maintenance times to end prior to the Kometa Scheduled run time.
For more information on Plex Maintenance, see https://support.plex.tv/articles/202197488-scheduled-server-maintenance/
Page 9/10
This is not anything you've done wrong; Kometa cannot connect to github to download that file for some reason.
When I saw it, I got past it by reauthenticating Trakt. I have no idea why that would have affected this, unless doing so had some follow-on effects inside Kometa.
Others have gotten past it by creating a new github token or adding one.
Sometimes deleting the cache helps.
A huge thanks! A new token from Github did the trick. 👍