Jump to content

DaSlinky

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by DaSlinky

  1. Just had to hard cycle my unraid machine, was notified one of my dockers was unresponsive.  Tried to http and ssh to the machine, nothing.  

    What logs and where do I start looking to see what happened?  In the few years I've had this machine this is the first time I've had to bounce it like this.  

  2. I have a win10 VM as my daily driver and use it for games so speed is somewhat a consideration.  Would it be a huge issue to have domain set to PREFER (lose redundancy I assume) or should I have it set to YES (hope it crashes while on the array).  I've considered just copying the image over to the array on a weekly basis.

     

      Is this even an issue as all my files / docs/downloads are stored on the array and I'd just have to install a base os and remap to them.

  3. Been using my Windows VM for several months w/out issue.  Tonight it stuttered then I lost my mouse.  After I killed the VM session and started it back up my AMD sound was no longer being detected by Windows.  Its passed through, just not there in Device Manager or anywhere else.  

     

    Anyone have this happen?

  4. 5 minutes ago, JorgeB said:

    loop2 is the docker image, and it's corrupt so it needs to be recreated, because of the log spam can't see the problem with libvirt, but most likely it's because cache is completely full, free up some space, reboot to clear the logs and if still issues post new diags.

    A reboot resolved the docket error.  Lost all my VMware sessions but the images are still there at least. When I got off create a new image it threw the screenshot below. After I cycled the vm manager it tossed the liberty message. 

    89B98995-E7E7-4736-AA2B-E7D4B147CFD3.png

    tower-diagnostics-20210318-0740.zip

  5. 1 hour ago, xxxliqu1dxxx said:

    Did you add 6000 to ADDITIONAL_PORTS as well as adding it the "old way"?

    **I was getting restricted port on ios, so i moved it to 8088**

    added the additional ports variable, verified the key was proper, have 9117, 8088 

    I also have 9117, 8088 as VPN_INPUT_PORTS

    VPN_OUTPUT_PORTS is blank/empty

    added additional port JACKETT, container port 9117, host port 9117 connection type TCP

  6. i think im getting to the end of my list of things to try, there is something external going on here, check firewall, check vlan's, try another browser, try another pc/device, ensure you are doing all of the previous on your lan NOT over a vpn to your home network, as this just adds complexity.

    I tried my HP laptop, iPad, MacBook(intel) and a win10 VM from unraid machine itself(daily driver) on the 192.xxx network. Same thing.

    Tempted to send you vpn credentials so you can work on it directly [emoji1787]


    Sent from my iPhone using Tapatalk
  7. 6 hours ago, binhex said:

    with an ip in the 192.168.1.x range right?

    So... out of freaking curiosity I did a route print and enclosed it.  It did not work but I'm VPN'd into my home network (at this time) being assigned a 172.x.x.x address.

    192.168.128 is my address scheme at the office.

    172.27.224.9 is my VPN address into my home network, that is set to be the 192.168.1.x

     

    Just got home have 192.168.1.155 as a local address... still no UI when i goto 192.168.1.159:6000

    😅

     

    UPDATE!

    Not the best of news, but at this stage Sonarr / Deluge / Jackett are all talking to each other.  The big rip is I can't see the Jackett webUI.  

     

    Of all things I guess that's the LEAST of my worries, I'd rather not have to monkey with the port/network parameters to do a full reconfigure.. but once that's done its done?

     

    I hope you're still game to get the webUI working, I am 😁

     

    image.png.88a33cb54e81e3a6100ab7d4f0c4c988.png

     

  8. 3 minutes ago, binhex said:

    iptables -S

    sh-5.1# iptables -S
    -P INPUT DROP
    -P FORWARD DROP
    -P OUTPUT DROP
    -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A INPUT -s 138.199.27.241/32 -i eth0 -j ACCEPT
    -A INPUT -s 138.199.27.221/32 -i eth0 -j ACCEPT
    -A INPUT -s 138.199.27.231/32 -i eth0 -j ACCEPT
    -A INPUT -s 138.199.27.232/32 -i eth0 -j ACCEPT
    -A INPUT -s 138.199.27.212/32 -i eth0 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
    -A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 9117 -j ACCEPT
    -A INPUT -i eth0 -p udp -m udp --dport 9117 -j ACCEPT
    -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
    -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A INPUT -i tun0 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A OUTPUT -d 138.199.27.241/32 -o eth0 -j ACCEPT
    -A OUTPUT -d 138.199.27.221/32 -o eth0 -j ACCEPT
    -A OUTPUT -d 138.199.27.231/32 -o eth0 -j ACCEPT
    -A OUTPUT -d 138.199.27.232/32 -o eth0 -j ACCEPT
    -A OUTPUT -d 138.199.27.212/32 -o eth0 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
    -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 9117 -j ACCEPT
    -A OUTPUT -o eth0 -p udp -m udp --sport 9117 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
    -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
    -A OUTPUT -o lo -j ACCEPT
    -A OUTPUT -o tun0 -j ACCEPT
    sh-5.1# 

  9. 5 minutes ago, binhex said:

    not required for jackett, this is used when you want to talk from a container running inside the vpn network to another container running on the lan, this is not the case for jackett.

    Not to create a tangent, I would have to do this for Sonarr to talk to Jackett then?

     

    restarted and went to 192.168.1.159:6000  no web interface.

    ServerConfig.json

  10. 17 minutes ago, binhex said:

    im running out of those, been doing support fallout for days!.

     

    ok can you screenshot ADDITIONAL_PORTS env var, i want to ensure the key is set not just the name, also can you set VPN_INPUT_PORTS also to 9117 PLEASE :-).

     

     

    Done, Should I do something for VPN OUTPUT ports?

     

    D6.jpg.9560a8d198ec63cada1a0d4c3b6921df.jpgD5.jpg.f069aaac3fb5a604e96204b3a535fcae.jpg

  11. 1 hour ago, binhex said:

    when you say no webui option, do you mean you dont see the 'web ui' when you left click jackett?, if so that is completely expected, it wont be there, as its now routing through delugevpn, you need to fire up a web browser and navigate to http://<your host ip address>:6000

    Configured the the ENV VAR as a VARIABLE as shown above, the Jackett entry as well, browse to http://192.168.1.159:6000 and nothing.  Shutdown the array and rebooted the entire system (someone said that worked for them), same thing.   

  12. 20 minutes ago, binhex said:

    'magic sauce' is the ADDITIONAL_PORTS env var, this punches holes in the firewall to allow you to connect.

    I see you stressing the ENV VAR pretty hard.  In my earlier Deluge build I had the Additional Ports already supplied, apparently in the one from last night its no longer there.  I need to add this as a VARIABLE and not a PORT with the below settings.

     

    I have Jackett PORT entry as Contrainer Port: 9117, HOST PORT 6000

    Additional Entry as below.

     

    Save/apply all settings

    Start DelugeVPN, validate its getting different IP

    Start Jackett, validate its getting the same IP as Deluge

    No WebUI option

     

    image.png.fa5bf7c6a851227f99772465a25e27cf.png

  13. 13 minutes ago, binhex said:

    nearly correct, you didnt remove ALL ports from jackett, please do this.

     

    correct, and yes multiple ports, with comma to separate.

     

    to be clear this is NOT a env var, create a port and define the the 'host' side of the port, port has to be unused, can be whatever you want but most people pick 6000 range, has to be a single port only, if you need other ports then add more.

     

    again to be clear, this is not a env var, its the 'container' side of the port you just created in the above step.

     

    you really need to read Q24. it really is all explained in there to be honest:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

    Trust me, been over that more times then <insert explicative>.  I think its a knowledge barrier on my part.

     

    I went and removed the 9117 in Jackett.  I leave the WebUI line alone or pull that out because the instructions in A24 say to remove all the ports.

     

    I was thinking those were 3  separate entries. They're to be two entries?  One for all the container ports (additional_ports, multiple) and  a single entry per container, like the one below.  This will route the traffic within the Deluge VPN and over to Jackett?

     

    image.png.cde46e5d5c2b593f7098dc4dc29a50b5.png

  14. 1 hour ago, binhex said:

    are you routing your containers through a vpn enabled container OR are you using privoxy and setting the proxy settings for your applications?.

     

    saw the screenshots above, ok so you are routing jackett (and others, but lets concentrate on jackett) through delugevpn, i see from the screenshot you have added in port 9117 (jacketts default port) to ADDITIONAL_PORTS, a good start!, HOWEVER you are missing the port itself, you need to add the port to the delugepvn container too, without that there is no connection from host to jackett.

     

    so add a new port to delugevpn, host port. = <whatever you want as long as its not in use> e.g. 9117, and then container port of 9117 (do not change this).

    I orphaned my DelugeVPN last night... so I'll have to recreate this.  So i'm clear can you validate that the Jackett settings are correct above and I'll be doing the following to the DelugeVPN container.

     

    Creating the following ports in Deluge.  Variable name in caps.

    • ADDITIONAL_PORTS: this will have whatever ports I need to forward.  9117 for Jackett.  This can/will house multiple ports.
    • HOST PORT: Pick some random unused port (is there a range?) Is this what is used for the WebUI? This is a single or can house multiple ports.
    • CONTAINER PORT: This has to match the container that's being routed.  Assuming a new one to be created for each routed container.

    I owe you a few beers come payday BinHex!

  15. 19 hours ago, mbc0 said:

    Hi removed binhex tag I posted on the wrong thread the other day, reposting on this, the correct thread as didn't want you to think I was ungrateful!

     

    I have managed to get all my containers talking to each other in your container now and can now access all my containers WebUI's and they are all talking to each other.  The answers were there in your guide & Q&A I just needed some help understanding a few things.

     

    Just wanted to say a MASSIVE thank you for your work, time and patience, it is HUGELY appreciated!

     

     

    @mbc0  What was your issue and how did you resolve it?  Just curious because i'm having a hell of a time getting my WebUIs on the containers to work.

  16. I've gone through all the setting, but for the life of me I cannot find where to do this from Q/A 25.  Everything appears to be wanting to route through the VPN, but there's no WebUI on my dockers now.

     

    Quote

    The other change you will need to do is when defining connections from an application to another application in the same container network (as is the case in this scenario) then you will need to set the host to 'localhost' and NOT the LAN IP address, this is because the applications are now bound to the same network and thus should communicate over 'localhost'.

     

×
×
  • Create New...