IMACRAB

Hello, I was able to get my prowlarr up and running with flaresolverr. While some indexers work without an issue, some other, bigger indexers are throwing up the following error message: Does anyone here know how to solve this issue? I can visit the websites in question manually from my browser without any issue.

Hey, hey, I looked into it again and both yours and also the 'official' docker didn't work initially. After ticking off the 'Use Proxy' options within prowlarr it worked however. Would you know if I just misconfigured the Proxy options for prowlarr in that case or was it never meant to work with 'Use Proxy' turned on? These were my options: Thanks again for your help!

Hey, hey, I was off for a moment myself - thanks for looking into it again. Yes, it's the IP address of my Unraid Server. For reference, prowlarr uses the exact same address, but with a :9696 at the end. The :8191 is also not used by any other docker.

Thanks for the tip. Is it this one? docker run -d --name='binhex-prowlarr' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Gordon" -e HOST_CONTAINERNAME="binhex-prowlarr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9696]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/prowlarr-icon.png' -p '9696:9696/tcp' -v '/mnt/user/appdata/binhex-prowlarr':'/config':'rw' 'binhex/arch-prowlarr' e55bf9753161d07da6aeb272004338a0f3b9fea8b369d53840417411057cf307 The command finished successfully!

What would be a good way to figure that out? I'm currently using mostly images made by you. That includes: FlareSolverr Prowlarr Sonarr QBitTorrent <- I should have succeeded to get my VPN up and running for this one

Thanks for coming back to me on this! That's very odd, because that is exactly what I did. I did not change anything throughout the installation of FlareSolverr either. And I got the following error from prowlarr when clicking to 'test':

Hey, hey, First of all: thanks @binhex for all that work! Insane what you are pulling off and make available. Thank you so much for that! I'm still new to the whole Home-Server, Docker and Unraid business. And even though I try to read through most of the documentation I do sometimes lose track of why something might not work in the end. Most of it all is still a new language to me. So, I thought I was on a good track with Prowlarr, Sonarr and friends but now require flaresolverr in order to use them. When I start flaresolverr however, the webUI shows the following: error: "Method not allowed." status_code: 405 I already installed python pack 3 but am kind of lost how to get it up and running. Installing Ungoogled-Chromium also didn't seem to help. Any idea or hint what the issue might be and how to solve it?

Worked perfectly, thank you so much!

Thank you itimpi. When I reset the array, will I have to reinstall and/or reconfigure my dockers? And before initiating it, should I disconnect the unwanted drive?

Hello there, I'm still fairly new to the community and in owning a home server. In my ignorance I thought I could just plug and unplug additional USB HDDs to my thin client like I would on my PC. Turns out I was wrong and simply disconnecting the HDD, which is unmountable anyway (Unsupported partition layout), results in not being able to boot up my array again. > Now my humble question is, how can I disconnect the HDD again? I don't want to format the disc - at least not yet. All I wanted to do is check 'real quick' if I can plug the HDD to access it's data through the network.

Hello UnRaid community, I'm glad to have found my way here and hope you all had a great start into 2024. I started 2024 in trying to setup my first 'Homelab' with a thin client working with Unraid. Thanks to one of those YouTube videos. And well, it went so-so so far. Needless to say, I'm still super new to the whole thing and have no real knowledge of networks and the whole jargon yet. In the end, those darn YouTube videos tend to make it seem sooo easy. At this point, I had no luck YouTubing and searching more, which is why I'm asking here. My general goal using Unraid on a thin client is the following: Use AdGuard to filter all outgoing requests Host one or the other gaming server, for friends to join Setup a plex library Set the thin client up as an additional internal storage solution The first big hurdle: I have an ISP Box (LiveBox 4 from Orange in France) It needs to remain touch point for internet access (192.168.1.1) I can deactivate it as a DHCP Server I can fix static IPs AdGuard (as a Docker solution via Siwat2545's repository) needs to be the DHCP Server to be able to filter traffic. When AdGuard is set up as DHCP Server - I lose the initial static IP of my thin client (and thus access to my Unraid) The thin client won't show up as a connection in AdGuard DHCP Server settings. The new thin client IP visible in my LiveBox after changing DHCP Server won't open the dashboard - just a 'no site' error. While the same IP address + the :180 (port I used) opens the Adguard dashboard without an issue. I could only ever get access to my Unraid dashboard again by restarting the thin client & having my LiveBox 4 play DHCP server again. Restarting both (not having AdGuard in autostart) and using the new assigned IP from the LiveBox. So, I'm not aware of how complex or simple this topic might be, but I'm clearly not sure what direction to take. Did I just forget to add /dashboard at the end of the new IP? TLDR: I want to use AdGuard as a docker from my ThinClient as a DHCP server for all traffic without losing access to Unraid's Dashboard. How can I do that?