Wilmo

A Comment

Ok, thanks for your help. Although it doesn't actually help explain what on earth is going on with AWS slowness... but., m'eh. I'll overwrite the USB tonight.

I am trying to upgrade from 6.3.5 to 6.4.1 but when the download of the ZIP file from the AWS is so slow! Like its been downloading for three hours now, and its only at 47%. Can anyone shed any light on this... its like AWS is purposly throttling the connection as I can download the file quickly on a different PC on a different network. Even if i use WGET from a command line it takes forever too... Where can i manually save the ZIP file so that the plugin updater sees it and uses that instead of having to re-download it again and again?

I have an unraid server with multiple network cards. two of the nics are used on a pfsense VM to provide me with a virtual firewall/router. pfsense has my no-ip.com dynamic dns set up on it. pfsense also has some ports forwarded for PLex, Emby, Sickrage etc... When i nmap my ddns name from Server-A (In south africa) I can see only the ports I have specifically forwarded. GREAT! When i nmap my ddns name from Server-B (in the UK) I can see the ports i forwarded AND a load of other ports too! Like pop3, smtp, ftp, imap... LOADs of others that I have not specifically forwarded! When i nmap my ddns name from Server-C (also in the UK) I can see only the ports I have specifically forwarded. Please can anyone tell me what is going on?! I do not want these odd ports open. But apparently they only appear to be open from my place of work... which I have not specifically allowed in PFsense or anything. I just don;t understand why some ports can be seen from one place, and not the other!

Thank you for your help on this... <edit> * ok... so... after weeks of struggling with this "problem" i asked a friend; who took ONE look at it and within about 3 seconds said..."there's your problem". IN Plex Settings --> Server --> Remote Access ... you have to put a tick in the "Manually specify public port" and then input the port you forwarded by your router. * For some reason I assumed that you would only use this if you were chanign the default port from the standard 32400. * So... PROBLEM FIXED! Thanks /u/fuckmywetsocks </edit> Port forwarding in your firewall doesn't have anything to do with your internal network. So for docker containers to speak to each other you have to use the ports you configured the containers to use. If you want one container to speak to another you use the IP of unraid and the port of the container you want to connect to. I haven't set up any apps to talk to plex, so don't know how to do it. I didn't think any one could talk to plex, but plex only looks for changes in your library and then adds the new content. So what are you trying to do? You said that transmission and other containers couldn't talk to plex, but now you say they can talk to each other? Are you trying to get the containers to talk to a plex server outside your network? Or simply trying to access your containers from outside your network? Be sure that you use unraids IP in sophos, as aptalca says in the post above yours and that you use a port that is mapped in your container template.

Thank you for your input. It was helpful indeed. Turns out i needed to put a tick in the "manually specifiy public port" Thanks for your help.

By default, the Plex Docker image uses "Host" ... so i just left it at that.... I'm beginning to think that this is not Docker, but something to do with the Plex connection checker. I'll keep plugging away.

Hello again, To clarify, specifically I am trying to use my Plex docker image outside of my network. Because Plex uses port 32400 to access any given Plex server from outside, I;ve forwarded the ports via Sophos. However, upon testing open ports on my plex server from outside my network ... (by simply using the native Plex "server --> Remote Access --> retry" button). I receieve the response "Not available outside your network" when it totally should be becuase all the necessary ports are forwarded! Likewise... when i try to forward torrent traffic on a specific port in Transmission, Transmission consistently reports that the designated port is Closed. So... thanks for your input. I'm just going to keep plugging away until I get something sorted. Port forwarding in your firewall doesn't have anything to do with your internal network. So for docker containers to speak to each other you have to use the ports you configured the containers to use. If you want one container to speak to another you use the IP of unraid and the port of the container you want to connect to. I haven't set up any apps to talk to plex, so don't know how to do it. I didn't think any one could talk to plex, but plex only looks for changes in your library and then adds the new content. So what are you trying to do? You said that transmission and other containers couldn't talk to plex, but now you say they can talk to each other? Are you trying to get the containers to talk to a plex server outside your network? Or simply trying to access your containers from outside your network?

Thanks for your input, although I think you mis-understand... my docker images can talk to one another on their designated ports fine. Its the EXTERNAL access that I cannot acheive... i.e. access to a docker image from outside my network Thanks Port forwarding in your firewall doesn't have anything to do with your internal network. So for docker containers to speak to each other you have to use the ports you configured the containers to use. If you want one container to speak to another you use the IP of unraid and the port of the container you want to connect to. I haven't set up any apps to talk to plex, so don't know how to do it. I didn't think any one could talk to plex, but plex only looks for changes in your library and then adds the new content.

Thanks for your response! If i set the docker image to "host" it carries the 192.168.1.X address of my network. If I set the docker to "bridged" it carries a 172.xxx.xxx.xxx address... which is no good as it isn;t on my network! :-) Port forwarding in your firewall doesn't have anything to do with your internal network. So for docker containers to speak to each other you have to use the ports you configured the containers to use. If you want one container to speak to another you use the IP of unraid and the port of the container you want to connect to. I haven't set up any apps to talk to plex, so don't know how to do it. I didn't think any one could talk to plex, but plex only looks for changes in your library and then adds the new content.

<edit> * ok... so... after weeks of struggling with this "problem" i asked a friend; who took ONE look at it and within about 3 seconds said..."there's your problem". IN Plex Settings --> Server --> Remote Access ... you have to put a tick in the "Manually specify public port" and then input the port you forwarded by your router. * For some reason I assumed that you would only use this if you were chanign the default port from the standard 32400. * So... PROBLEM FIXED! Thanks /u/fuckmywetsocks </edit> I've paid £80 for a plus license, and am having difficulties with UnRAID... I emailed limetech directly but never had a response. Please can someone help me understand port forwarding to Docker images in UnRAID. Specifically, Plex. My firewall/router/DHCP/Gateway/DNS is a VM on UnRAID (Sophos UTM). This works fine. I can surf the internet. I;ve got the plexinc Docker image set up, and have forwarded all the relevant ports from Sophos UTM, to the internal IP address of the UnRAID server. However, Plex / Transmission / any other Docker permenantly reports that they cannot connect to the Plex server on the forwarded port. It doesn't seem to matter if the Docker image uses "host" or "bridged" network set up... the ports are never opened properly. However, on a actual physical machine on my network, port forwarding works fine. So its got something to do with Docker. I;ve searched and asked questions on reddit etc... and peoples response are usually "well that should work fine... so we can;t help". Please can limetech offer some advice on port forwarding for Docker images?