• Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

485 profile views

xxDeadbolt's Achievements


Apprentice (3/14)



  1. Thanks guys, will give it a go tomorrow. Think I was expecting a full file name instead of a wildcard type, like you’ve said @Mystic. I was rummaging through the dirs earlier looking for a file ending .env or something 😄 Edit: That's it working now, thanks again folks!
  2. Thanks for this, wondered what was up with Heimdall! I don't understand what you mean by this part, though, could you dumb it down a little for me, please? I'm not seasoned with modifying things through the terminal this way.
  3. No worries, thanks for the help Edit: After a few minutes, all the indexers appeared in Radarr & Sonarr, in case anyone has the same "issue". Seems my impatience was the source of that one, though!
  4. Awesome, thanks, adding the ignored address seems to have done the trick! Just t check as well, will Prowlarr auto add any indexers into radarr/sonarr? Some have appeared, but not all. Does it periodically check for new ones and add them?
  5. Hey - I've moved over to this & having a little issue. I've got it set up, added Radarr/Sonarr & Qbit VPN (all your containers), but when I tell Prowlarr to use the proxy, I can't connect to Qbittorrent. Radarr & Sonarr still connect, though, & all my indexers test OK which some don't when proxy is off. Can't quite figure out where I'm going wrong, tried testing Firefox on a different machine on the LAN to check the proxy was working, which it is. Any nudges in the right direction would be appreciated... (didn't provide any info on the mappings as I wasn't 100% sure if it was Prowlarr or Qbit, but if anything is needed let me know)
  6. Strange, I've literally just dealt with this about an hour ago (it was sitting at around 40Gig!). I used the unraid terminal to delete the numbered folder, & it's contents, in the Sync+ directory. Wasn't sure if just deleting the Sync+ folder would make a difference, but decided to just keep it and delete everything in it. So far, no issues.
  7. Yep, UPnP was enabled. So, I'd already set the port forward manually... I just didn't think to try completing the set up & seeing if it worked anyway. That error made me fixate on it; however, it's set up & connecting fine. Thanks for the nudge, not sure why the UPnP client isn't playing ball with my router, but it works!
  8. Trying to set this up & encountering an issue with UPnP/port forwarding. I'm getting the remark "UPnP: forwarding not set" & "The Local endpoint resolves to xx.xx.xx.xx. In most cases, this should be your public WAN IPv4 instead: xx.xx.xx.xx", where xx.xx.xx.xx show my correct public IP, on both mentions in the message. This is the port forward on my router: & it also shows UPnP is enabled: I'm using DuckDNS & it's working fine for other services, but this just doesn't seem to change. I've also set the "Local gateway uses UPnP" setting to both yes & no, with no change. When set to No, it shows "Remark: configure your router with port forwarding of port 51820/UDP to" instead of "UPnP not set" & when set to yes, it just says the message as above. I don't have anything special/complex going on in terms of my network, so not entirely sure what's going on. Anyone any pointers?
  9. Getting the same thing here, can't see anything in the syslog either. Possibly the update itself?
  10. That’s weird, I checked the language thing & Chrome was set to ‘English’ in there, too. I changed it to ‘English (UK)’ and removed any other variant, relaunched but still the same behaviour. However, I’d gone to the ‘Manage extensions’ setting, as I’d realised I had more than the 2 I’d mentioned before (they were hidden, instead of displaying on the toolbar, so slipped my mind) Disabled them and the search started working. Enabled them one by one, but it worked each time. So I’m not sure which one was interfering, but it seems one of them was. If this behaviour starts again, I’ll disable one at a time & check again, but it seems to be working again for now. Cheers
  11. Updated to latest version of CA & getting new behaviour, when searching, in this pop up error message: Here's the console errors: Edit: Forgot to add CA debugging log CA-Logging-20210516-1832.zip
  12. Search doesn't work at all. Autocomplete will show things as I type, but hitting enter, or clicking on one of the autocomplete options, does nothing.
  13. Sorry to piggyback, I'm also getting this behaviour in Chrome & Brave. Firefox sometimes/rarely works, at first attempt, then I get this issue. I don't have any add-ons in FF, Chrome only has Bitwarden & iCloud bookmarks. Strange.
  14. That's odd - only seen that a couple of times since I started using unraid, but usually fixed by enabling Advanced view & then 'force update'.