Jump to content
binhex

[Support] binhex - Medusa

39 posts in this topic Last Reply

Recommended Posts

Overview: Support for Docker image arch-medusa in the binhex repo.

Application: Medusa - https://github.com/pymedusa/Medusa/

Docker Hub: https://hub.docker.com/r/binhex/arch-medusa/

GitHub: https://github.com/binhex/arch-medusa

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here


If you appreciate my work, then please consider buying me a beer  :D

 

btn_donate_SM.gif

Edited by binhex

Share this post


Link to post

I've had issues with 2 Medusa updates, and am generally nervous about updating. Is there a simple way to apply an update and test it out, but then be able to revert back to the prior version if there are issues?

Share this post


Link to post

Sorry, realizing this was the binhex thread. I am running the LinuxServer version. Is there a similar link for those tags?

Share this post


Link to post
Just now, SSD said:

Sorry, realizing this was the binhex thread. I am running the LinuxServer version. Is there a similar link for those tags?

lol I guess the dashboard / docker app context menus only work when they're used.

 

Easiest way to figure out any apps available tags is from CA go to installed apps, hover over / click on the icon for the app then click the dockerhub link on the pop up and navigate to tags

Share this post


Link to post

Your CA is way out of date

2017.09.13
Changed: Clicking Repository from popup will now search for applications contained within the repository
Added: App info popup now has link to go directly to docker hub page for application
Fixed: Prevent possibility of duplicate app appearing in app of the day.
Enhanced: Previously, app of the day would return errors if unRaid CSS and window width support horizontal resolution greater than 5700 pixels.
Fixed: If multiple browser tabs opened to apps tab, detect if app database is out of sync between windows and update tab accordingly.
Changed: Allow moderation to whitelist an application without appfeed update

 

Share this post


Link to post

Thanks!

 

Is there a way to know what release number I last installed? binhex uses the app's version number which would make it easier to figure out.

Share this post


Link to post
1 minute ago, SSD said:

Thanks!

 

Is there a way to know what release number I last installed? binhex uses the app's version number which would make it easier to figure out.

Not that I know of if you're just running :latest and not updated.

Share this post


Link to post

I wonder if anyone can help. I can't seem to get the NZBtoMedia post-processing scripts to run. I keep getting the error below when NZBGet runs the nzbToSickbeard script:

 

Unable to figure out what folder to process. If your download client and Medusa aren't on the same machine, make sure to fill out the Post Processing Dir field in the config.

 

Have followed the instructions on from the main github page for NZBtoMedia but still no luck - https://github.com/pymedusa/Medusa/wiki/NZBtoMedia

 

Here is a screen of my Medusa Congfig, tried turned off/on automatic post processor still the same. I wan't to avoid Medusa constantly scanning my disks even though in SpaceInvader's tutorial for SickRage he says ignore the warning and turn the option on. Just leave the path to scan as blank and the script will do the rest. I have the default scripts from NZBtoMedia site and configured NZBGet and Medusa as required.

 

Thanks All

Medusa-Post.PNG

 

NZB Get Paths.PNG

NZBtoSickbeard.PNG

Edited by witalit

Share this post


Link to post
3 hours ago, witalit said:

I wonder if anyone can help. I can't seem to get the NZBtoMedia post-processing scripts to run. I keep getting the error below when NZBGet runs the nzbToSickbeard script:

 

Unable to figure out what folder to process. If your download client and Medusa aren't on the same machine, make sure to fill out the Post Processing Dir field in the config.

 

Have followed the instructions on from the main github page for NZBtoMedia but still no luck - https://github.com/pymedusa/Medusa/wiki/NZBtoMedia

 

Here is a screen of my Medusa Congfig, tried turned off/on automatic post processor still the same. I wan't to avoid Medusa constantly scanning my disks even though in SpaceInvader's tutorial for SickRage he says ignore the warning and turn the option on. Just leave the path to scan as blank and the script will do the rest. I have the default scripts from NZBtoMedia site and configured NZBGet and Medusa as required.

 

Thanks All

Medusa-Post.PNG

 

NZB Get Paths.PNG

NZBtoSickbeard.PNG

 

WOW. It was something SO DAMN simple, I spent hours trying to work this out lol. The folder mapped under Medusa & NZBGet was not exactly the same I had to drill 1 folder up for Medusa so:

 

NZBGet on Docker = /mnt/user/NZB Downloads/ 

Medusa on Docker = /mnt/user/NZB Downloads/

 

Both of these are for the /data folder under the template.. just an FYI in case anyone else sees this issue. 

Edited by witalit

Share this post


Link to post

Is anyone using this with Jackett? I cannot for the life of me get it to work. I have the latest binhex/arch-medusa running (rebuilt from my Sickrage media, but not database). This worked fine, and things were up and running. My downloader is deluge-VPN, which I've always gotten to work via WebUI. Deluge also looks a a folder /downloads/jackett/ for torrents. 

  It seems that Medusa is passing the request just fine to Jackett, but can't deal with what it gets back. Jackett has a "black hole" setting, but it doesn't actually seem to put anything in there on normal requests, just manual downloads that I tell it to put there.

  Apologies in advance for the jpg spam, but I'd really like to figure out why Jackett isn't pushing the torrent or magnets back to Medusa in a way that can be passed to deluge.

 

  Thanks to anyone with enough insomnia to look at this one. As I look over the stuff, I'm wondering if the issue has something to do with medusa not handling the magnet links well. That reminds me of some SR issues I think I had before, but I can't remember that cause/solution. 

 

Edit: Replying to myself here--It was a medusa side issue that they've fixed by adding explicit Jackett providers. Sadly you can't treat all of Jackett as one provider, and have to configure each separately, but it's working with Jackett.

 

Thanks! 

josh

 

 

 

 

 

 

 

 

 

Edited by uiuc_josh
senility, subsequent self-answered question.

Share this post


Link to post

Medusa is broken for Torrentleech search provider, its been fixed in Github for medusa a few days ago.

Can we get an update on the docker please :)

 

2018-04-07 15:30:49 INFO SEARCHQUEUE-FORCED-75692 :: [TorrentLeech] :: [d6eb72d] Unknown exception in url https://classic.torrentleech.org/torrents/browse. Error: Unable to parse Cloudflare anti-bots page: Error parsing Cloudflare IUAM Javascript challenge. Cloudflare may have changed their technique, or there may be a bug in the script. Please read https://github.com/Anorov/cloudflare-scrape#updates, then file a bug report at https://github.com/Anorov/cloudflare-scrape/issues." Cloudflare may have changed their technique, or there may be a bug in the script. Please read https://github.com/Anorov/cloudflare-scrape#updates, then file a bug report at https://github.com/Anorov/cloudflare-scrape/issues."

Share this post


Link to post

I keep getting Torrent file contents are empty when I download anything from torrentleech. Since Sunday anyone know how to fix that?

Share this post


Link to post

Hello.

 

I've just installed unRaid on a new homebuilt nas

on this server i've installed binhex - rTorrentVPN which works flawelessly! i've setup the autodl-irssi and it works like a charm!

 

then i went on in my intall process of a fully functionall nas and installed binhex - Medusa

 

but this is where i ran against the wall.. i cant connect to the rtorrent with the username and password i use to rutorrent(the default for now)

 

my nas is called NasBox as servername, has the static IP 192.168.1.99

im connection trough my browser to 192.168.1.99:9080 to rutorrent

 

i have also tried to use all these in order to connect

scgi://localhost:5000

and localhost:9080

https://localhost/rutorrent/plugins/httprpc/action.php

 

all off the above i have tried with basic http authentication AND none.

Screenshot_1.png

 

i have also attached som screenshots of the settings i've installed the dockers with.

 

Screenshot_2018-08-11 NasBox UpdateContainer.png

Screenshot_2018-08-11 NasBox UpdateContainer1.png

 

please let me know if need to give any more information.

Edited by JaRi
more information

Share this post


Link to post
On 8/11/2018 at 4:46 PM, JaRi said:

but this is where i ran against the wall.. i cant connect to the rtorrent with the username and password i use to rutorrent(the default for now)

 

ok first thing to check is that you have defined LAN_NETWORK correctly. see here if you are unsure Q3.:;-

 

https://lime-technology.com/forums/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

assuming thats correct, have a look at this screenshot linked below, this is how sonarr should be configured to talk to rtorrentvpn, replace ip address of host with your unraid servers ip:-

 

https://github.com/binhex/images/blob/master/docker/config/sickrage-rtorrent.png

 

 

Edited by binhex

Share this post


Link to post

This is what ifconfig looks like on the unraid server - picture attached.

i have tried every combination i can think of from that ifconfig and still cant connect from medusa. 

Udklip.JPG

i have added this screenshot aswell. because i lastly ran against a funny wall.. no matter what adress i specified on install it was alwasy 172.17.0.2 in port mapping.

Udklip2.JPG

Edited by JaRi

Share this post


Link to post
16 hours ago, JaRi said:

This is what ifconfig looks like on the unraid server - picture attached.

i have tried every combination i can think of from that ifconfig and still cant connect from medusa. 

Udklip.JPG

i have added this screenshot aswell. because i lastly ran against a funny wall.. no matter what adress i specified on install it was alwasy 172.17.0.2 in port mapping.

Udklip2.JPG

 

ok firstly ignore output from ifconfig, this wont get you far, docker has its own internal network, as you have found out its by default (yes you can change it) set to 172.17.0.0/16 but you dont need to worry about this, the docker daemon will take care of routing etc so ignore it. 

 

so looking at your config it looks ok, so rtorrentvpn is configured correctly (apart from the fact you have disabled the vpn part, but thats your choice), take a look at the following screenshot, your config for medusa should look like this, set <docker host ip> to 192.168.1.99 and then test:-

 

https://github.com/binhex/images/blob/master/docker/config/sickrage-rtorrent.png

 

Share this post


Link to post

Thanks! that did the trick :) i can now connect and its perfect.!

 

 

Edited by JaRi
found the answer my self.

Share this post


Link to post

Hi,

 

Seems this version of Medusa is pretty outdated or there is some issue. I keep getting an error about 'Unknown version' and my config was lost.

 

Can you advise if this is latest master build of Medusa? 


Thanks Binhex!

Share this post


Link to post
Just now, witalit said:

Hi,

 

Seems this version of Medusa is pretty outdated or there is some issue. I keep getting an error about 'Unknown version' and my config was lost.

 

Can you advise if this is latest master build of Medusa? 


Thanks Binhex!

This is the latest github 'release' i only update on releases not when commits are done to the master branch, this is to try and ensure stability as much as possible.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now