@s3cur17y wrote:
Ok, so recently I upgraded to version 2.10.95 and now my config.yml isn't working. Could someone please give me a hand.
feeds: rss: https://someurl.com iptorrents: rss_key: hjbnjhn uid: 8908989 password: SuperSecretPassword! category: - TV-480p - TV-SD-x264 - TV-XVID folders: exists_series: - /media/2TB_New/TV/ download: /home/user/.torrents my_shows: series: - They Found Hell - American Horror Story - Bates Motel - Ghost Adventures - Dual Survival - Simpsons - The Strain - Tosh.0 - The Last Man On Earth - The Slap - Dig - American Crime - Fear The Walking Dead - BlindSpot - Alaska Haunting - Heroes Reborn - Alaskan Bush People - Survivorman - Lucifer - 60 Days In - Damien jeffs_shows: series: - Ray Donovan - The Big Bang Theory - The Flash - The Librarians - Blue Bloods - Arrow - Grimm - Game of Thrones - Vikings - Teen Wolf - Supernatural - Homeland - The Amazing Adventures Of Gumball - Daredevil common_shows: series: - American Dad - Better Call Saul - Family Guy - Gotham - Person Of Interest - Scorpion - South Park - The Blacklist - The Walking Dead - True Detectives - Mr.Robot - Zoo - Ash vs Evil Dead tasks: do_htpc: template: - feeds - folders - my_shows do_bluebeast: template: - feeds - folders - jeffs_shows do_both: template: - feeds - folders - common_shows schedules: - tasks: - '*' interval: minutes: 15 web_server: bind: xxx.xxx.xxx.xxx port: 3539 api: yes webui: yes
Error Log:
2017-10-05 14:12 WARNING check Config line 2 is indented too much 2017-10-05 14:12 WARNING check Config line 69 is not indented enough 2017-10-05 14:12 WARNING check Config line 69 is indented incorrectly (previous line ends with ':') 2017-10-05 14:12 WARNING check Config line 90 is indented incorrectly (previous line ends with ':') 2017-10-05 14:12 VERBOSE check Pre-checked 92 configuration lines 2017-10-05 14:12 CRITICAL manager while parsing a block mapping in "<unicode string>", line 1, column 1: feeds: ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 11, column 3: folders: ^ ------------------------------------------------------------------------------- Malformed configuration file (check messages above). Common reasons: ------------------------------------------------------------------------------- o Indentation error o Missing : from end of the line o Non ASCII characters (use UTF8) o If text contains any of :[]{}% characters it must be single-quoted (eg. value{1} should be 'value{1}') Reason: expected <block end>, but found '<block mapping start>' Check configuration near line 0, column 0 Check configuration near line 10, column 2 Fault is almost always in one of these lines or previous ones 2017-10-05 14:12 CRITICAL manager Failed to load config file: Config file is not valid YAML Could not start manager: Config file is not valid YAML
Posts: 1
Participants: 1