Jump to content

morreale

Members
  • Content Count

    50
  • Joined

  • Last visited

Community Reputation

0 Neutral

About morreale

  • Rank
    Advanced Member
  • Birthday 03/12/1971

Converted

  • Gender
    Male
  • Location
    New Orleans, Louisiana
  • Personal Text
    ...Storing all the things since 2012...
  1. Purchased my first Unraid Pro license June, 11, 2012. Havent looked back. The product itself and the extensibility is so amazing!
  2. perfect thanks so much! might need to edit your posts since the two links seem to be missing "forums" downgrade to v6.3.5 replace cache procedure
  3. so far so good. i can't thank you enough. can you elaborate at all at what you had to do?
  4. everything functions properly as stated except for the post processing script. which in my case tries to establish a connection from the sab container to the sickbeard container over port 8081. i think the issue is simply that the port is not allowed to leave the sab docker container. i think an allow of that port (or whatever port is configured for sickbeard) will solve the issue. thanks for taking the time to look into this.
  5. Thanks binhex. Is there a guide or something you can point me to that explains how to edit the IPTables inside the container? something like this? https://lime-technology.com/forum/index.php?topic=40290.0
  6. that functionality works fine. the piece that doesn't work is a post processing task that tries to hit a URL on a certain (user defined) port inside the sickbeard container.
  7. pretty sure this is where the problem lies... this shows the only ports allowing traffic are 443 (vpn) and 8080/8090 (sab) i need to add 8081 to this table to allow this container to communicate out to my sickbeard container. (or some translations on both containers) playing around with adding a port to the docker config. 2016-06-29 20:00:44,151 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2016-06-29 20:00:44,154 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT
  8. assume you're referring to the same issue I am? SickBeard post processing? yes I was the one who posted this a while back in this thread. Sorry you are having the issue but also glad I am not the only one. It was driving me crazy. Ah, Roger. Thanks for the original post. I thought I was the only one. Fingers crossed we can get this addressed. It's near perfect the only thing i can think of is we need to configure the ports/iptables to allow traffic to pass over the port (8081 in my case) from sab to sickbeard
  9. assume you're referring to the same issue I am? SickBeard post processing? yes I was the one who posted this a while back in this thread. Sorry you are having the issue but also glad I am not the only one. It was driving me crazy.
  10. still nothing on this? just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.
  11. yeah it must have been added in .08 which became 1.0 but it shows in the old plush interface as well.
  12. While in SAB you can click the Status tab and then the Dashboard tab and you will see the Public IPv4 Address it is connected with.