Hogwind

Members
  • Posts

    103
  • Joined

  • Last visited

Everything posted by Hogwind

  1. Best way to trouble shot is to look in the log file. A quick way is to open the log after you started the docker through the docker menu. For all the logs look in \appdata\sonarr\logs
  2. Source: https://wiki.servarr.com/radarr/faq#can_I_disable_the_refresh_movies_task
  3. How did you set up your download client in Sonarr? Has it been working and all of a sudden it has started behaving this way?
  4. The logs contains Kill Bill Vol. 1 2003 Bluray-1080p.mkv, maybe the file is damaged or something. I would remove it and refresh the share.
  5. I think you can leave chown Group empty if you don't use remote shares. Hopefully you have by now got it working...
  6. Check the Permissions under Settings > Media Management, I've got mine set like this and haven't had any issues. What's your current permissions settings?
  7. I think it's a Overseerr setting, check that you have Enable Automatic Search under Settings > Services > Radarr.
  8. I think it's a prowlarr setting. Do you get a green check when you run a test of the radarr app in prowlarr? Here is a guide that covers most of the setup.
  9. Maybe you changed the owner/premission of config.xml when you edited it. EDIT: default is nobody/-rw-r--r--
  10. Looking at the log it says: System.Exception: database disk image is malformed I don't have any experience myself with that but I found and posted some info about that issue, if you check one page back. I would test one of the backups you will find in the appdata -> radarr -> backups folder.
  11. First I update from Action Centre: And then when you check the Docker page it still has an update: But I have now noticed that the "update ready" and the blue text disappear after a while, maybe after the next check for an docker update?
  12. Hi, if you update dockers from action center, the dockers gets updated. But on the unraid dashboard you still see the updated dockers with blue text and under dockers you se the lightning indicating that there still is an update. unRAID 6.10.3 CA 2022-07-26
  13. Hi, looks like you got the same problem as some users of binhex radarr docker. Picture with info from that thread. Source: https://forums.unraid.net/topic/53807-support-binhex-radarr/page/21/
  14. What I did was edit the docker template and added Repository: linuxserver/qbittorrent:14.3.2.99202101080148-7233-0cbd15890ubuntu18.04.1-ls110 It worked for me but I don't know if it's the correct one to use in unraid.
  15. Seems like the latest(v4.3.3) update is broken, it doesn't load the old torrents. Does anyone have the Repository tag for v4.3.2, there are so many to choose from. EDIT: I just tried this linuxserver/qbittorrent:14.3.2.99202101080148-7233-0cbd15890ubuntu18.04.1-ls110 And it worked, but if it's not the correct one i'm happy to be corrected.
  16. Yes, the error message is correct. Both Radarr and Deluge need to have the same container path for downloads. Now Radarr have /downloads and Deluge have /data/completed. You have two options, either you change the container path for Deluge downloads to /downloads or you change Radarr container path from /downloads to /data/completed.
  17. Did you change the path in the docker template? What is the path for all your movies in the Movie Editor?
  18. Follow this guide https://www.youtube.com/watch?v=HLcj-p-lcXY
  19. We seem to have similar problems. I solved my problems with an uninstallation of Bitwarden, also deleted the folder in appdata. And after that I installed it again with the same settings. Now everything works like a charm.
  20. I have the exact same problem as BrunoVic. The date/time is correct. The Bitwarden dockerlogs tells me this: [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [2020-03-20 09:00:11][ws][INFO] Listening for new connections on 0.0.0.0:3012. [2020-03-20 09:00:11][start][INFO] Rocket has launched from http://0.0.0.0:80 I have followed the guide that Spaceinvader One posted on youtube and used a xxx.duckdns.org domain. Is the letsencrypt config correct? resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name xxx.duckdns.org; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } }
  21. system.method.set_key has stopped working, is there a new parameter I can use instead? EDIT: Is there an easy way to roll back to rtorrent/0.9.6/0.13.6 ?
  22. Thanks for the answer. I will re-install the apps, and check the VM if something else made it disappear.