danielg

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by danielg

  1. 6 hours ago, CyaOnDaNet said:

    Interesting, I just pushed a new update so check your docker updates and apply.
    image.png.db0b4df6fc3f4fe062db6b4878d493d8.png

    The command `!bot info` should now state the bot version so if you see 1.1.4 then you have the latest. Let me know if you have the same issue after this update.

    image.png.7e39c869e450e5b365f354955aa6ba43.png
     

    Ahhh, had to switch to advanced view and force update. All is working now! Thanks :)

  2. 50 minutes ago, CyaOnDaNet said:

    I apologize for the sonarr bug, I actually pushed an update that broke it without realizing it. It's fixed now, if you go to your container and force an update it should be good. 

    Thanks for the quick response! Though, I'm not seeing an update and still have the same issue.

  3. Managed to get everything mostly working but I'm having trouble getting Sonarr to work. When I try to use a Sonarr command like "!notifications list" I get no response and in the logs it shows this. Any Ideas? 

    TypeError: Only HTTP(S) protocols are supported
    at getNodeRequestOptions (/app/node_modules/node-fetch/lib/index.js:1303:9)
    at /app/node_modules/node-fetch/lib/index.js:1404:19
    at new Promise (<anonymous>)
    at fetch (/app/node_modules/node-fetch/lib/index.js:1401:9)
    at sonarrService.getSeries (/app/src/sonarr.js:14:32)
    at Object.updateShowList (/app/index.js:828:40)
    at Object.execute (/app/commands/notifications.js:1274:25)
    at Client.<anonymous> (/app/index.js:218:12)
    at Client.emit (events.js:223:5)
    at MessageCreateHandler.handle (/app/node_modules/discord.js/src/client/websocket/packets/handlers/MessageCreate.js:9:34)
    Couldn't connect to Sonarr, check your settings.