Git Product home page Git Product logo

Comments (6)

icebal avatar icebal commented on July 19, 2024 1

Comment from the above link, for future reference:
You probably need to use the host_return option within the config.ini for mylar. Set it to the direct ip of your mylar installation, so that if you were trying to load something from mylar within sabnzbd it can be reached:
host_return = http://192.168.1.10:8090/

You can then leave the actual host address within mylar as 0.0.0.0 (or local host) and it will force sabnzbd to request the nzb360.com from the host_return ip when trying to grab the nzbs from mylar.

from docker-mylar.

lonix avatar lonix commented on July 19, 2024

Try useing the host ip rather than the container ip
fre. 11. mar. 2016 kl. 17.17 skrev wesley jackson <[email protected]

:

when Mylar snatches an NZB, it sends sab an URL back to Mylar to upload
the nzb. the issue with this is Mylar sends sab the docker ip address
instead of something sab can actually connect to. the work around for right
now is to setup black hole for sab, net=privileged , or link the containers
together. the url given to sab as an example is:

Trying to fetch NZB from
https://CONTAINERIP:8090/api?apikey=APIKEY&cmd=downloadNZB&nzbname=COMICBOOKNAME.nzb


Reply to this email directly or view it on GitHub
https://github.com/linuxserver/docker-mylar/issues/5.

from docker-mylar.

icebal avatar icebal commented on July 19, 2024

setting the ip to the host IP or hostname removes access to the webGUI, as does using anything other than 0.0.0.0. This is more of a mylar bug inside Docker, but still is an issue.

from docker-mylar.

icebal avatar icebal commented on July 19, 2024

Link to the issue on mylar's github:
evilhero/mylar#1094

from docker-mylar.

sparklyballs avatar sparklyballs commented on July 19, 2024

read the response from evilhero posted since your reply.

from docker-mylar.

hashmil avatar hashmil commented on July 19, 2024

I had the same issue. Can confirm that the below from @icebal is the definite fix (at least for me!)

"You probably need to use the host_return option within the config.ini for mylar. Set it to the direct ip of your mylar installation, so that if you were trying to load something from mylar within sabnzbd it can be reached:
host_return = http://192.168.1.10:8090/"

from docker-mylar.

Related Issues (15)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.