xxDeadbolt

Members
  • Posts

    160
  • Joined

  • Last visited

Everything posted by xxDeadbolt

  1. 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 192.168.0.103:51820" 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?
  2. Getting the same thing here, can't see anything in the syslog either. Possibly the update itself?
  3. 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
  4. 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
  5. 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.
  6. 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.
  7. 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'.
  8. Bit of a strange issue, when I'm searching for anything in the apps section, nothing happens. For example: I start typing 'rTorrent' and the pre-fill list of results display under the search box. I click it, & search box fills with it.... but nothing happens. I press enter, nothing happens. Same if I click on a repo name, then 'Search apps'. The search box fills with the repo name, but no results are shown, it stays where it is on the default 'New apps' section. Tried Chrome & Brave, seems to be ok on Firefox for a small window of time, then it'll start this behaviour eventually. Tried purging the settings, cache, history etc etc with no luck. Anyone else seeing this? EDIT: Forgot to add, Had no problems with 6.8.3, but since moving to 6.9.1 & 6.9.2 it's been happening.
  9. Mine has been working for a couple of weeks now with everything configured as above. Only problem I had was self-inflicted, where I initially entered the variable value as 'hcaptcha_solver' instead of 'hcaptcha-solver'
  10. Mine has a few more lines, though most autopopulated. I chose the Berlin endpoint, that's all I needed to manually edit: [Interface] Address = *[redacted]* PrivateKey = *[redacted]* PostUp = '/root/wireguardup.sh' PostDown = '/root/wireguarddown.sh' [Peer] PublicKey = *[redacted]* AllowedIPs = 0.0.0.0/0 Endpoint = de-berlin.privacy.network:1337 Forgot to say, I'm running rTorrentvpn, not Delugevpn, but the vpn config info should be pretty much the same (as far as I know)
  11. OK, so rebooted and got the diagnostic. The log mentions installing the plugins, but I don't know if that's normal or not. Plugins section don't show them as anonymous anymore... but going into that section takes a few seconds (roughly 8 seconds), whereas before it was pretty much instant. odin-diagnostics-20210310-1520.zip
  12. Yes, all my containers are still running, & the GUI is accessible, too. I can't get the diagnostic, though. In the GUI, it hangs on "downloading..." & in terminal, I get this: /usr/bin/php: error while loading shared libraries: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory I've not rebooted yet, was hesitant in case it made things worse.
  13. I've just had an issue, which seems to have been caused through trying to update some packages in the NerdTools plugin (although, I can't be usre this is what the cause is)... This shows whenever I go to Settings > Nerd Pack now & it just loops whenever I click Download. In the Plugins section, this is also now showing: I've tried removing & reinstalling the nerd pack plugin, but made no difference. Can anyone help?
  14. Awesome, 6.9.0 > 6.9.1 done. All seems to be running as expected. Thanks again!
  15. Just updated from 6.8.3 > 6.9 with no issues (so far).
  16. Just upgraded 6.8.3 > 6.9.0 with no issues so far. Everything seems to be running as it was, took less than 5 minutes. Removed the edited go file config for hw transcoding, then un-blacklisted the intel driver with touch /boot/config/modprobe.d/i915.conf Tested Plex and it's using hw transcoding fine. For something I was absolutely bricking it to pull the trigger on, it was absolutely seamless and hardly seems worth the fear now🤣 Cheers!
  17. haha yeah that's it. I can't remember setting the proxy manually in radarr/sonarr tbh, so I must've done it a long time ago & never had a reason to change it before now. All working fine now though 🙂
  18. Can I check - is the privoxy/port 8118 not able to be used with the iptable tightening now? I used the same proxy settings on radarr/sonarr and the indexers were failing in them until I removed it. I'm not entirely sure I need the proxy on them, tbh, when the indexer traffic is being routed through the vpn on rTorrent, but just wondering if this is what's affecting it.
  19. Think it's fixed now - for some reason, I had the proxy settings set to use the rTorrent/privoxy port 8118 in my jackett settings. I removed that, since it's routing through the container anyway and it's fine now. Cheers again!
  20. Yeah I've restarted jackett a couple of times, but still failing.
  21. Strange, all my indexers are failing now 😕
  22. Awesome, sorted! I assume this is the case, but just to double check: am I ok to delete the manual key I created for jackett to run through it, now that it's in the additional_ports? Edit: Oops, tried it and it broke again. Sorted once I added it back 🤣 Cheers binhex!
  23. Yup, routing it through your rTorrentvpn container.