Believe it or not I did spend 4 hours googling this and there are no updated guides on setting this up. The guides I find are missing most of these fields.

 

1- Network type:  Should I be using Bridge, Host, br0 or Custom?  And why? (please explain what this means. I'm using br0 for Pi-Hole but I don't know why)

2- What do I map for "Transcode"? I assume I'll need to transcode. What do I do here?

3- Can I close off some of these ports? 

4- How did I get upgraded to an "Advanced Member" when I'm probably the biggest idiot on here? 🤪

 

Edited October 18, 20196 yr by adminmat

Would LOVE to find a video guide on how to set up Plex in unraid. Funny SpaceinvaderOne didnt make one. 

 

got this:

 

 

 

Thanks for the links but I'm not understanding when you would use a Host network type over a Bridge. I have a ESXi host running with VMs. They each have their own IP address. Which the Plex docker doesn't get if it's set up as a Host network type. 

 

I have several VLANs on my network with firewall rules separating them for security. Do i need to set up the Plex docker in Bridge mode in order for my Plex to be passed to my IoT network Roku? I tried opening port 8324 and 32400 in my router so the Plex server and the Roku can communicate locally but it's not working. 

 

Any ideas?

 

 

So update:  I tried every combination of allowing ports within my network. And I can't get Plex to connect directly to the Roku. I am now trying Network Type br0 which gives Plex it's own IP address. Now I completely lost Remote Access (the slow 2mb/s connection). I still CAN connect and play directly when on the same network from within the LAN.

 

7 hours ago, adminmat said:

Thanks for the links but I'm not understanding when you would use a Host network type over a Bridge. I have a ESXi host running with VMs. They each have their own IP address. Which the Plex docker doesn't get if it's set up as a Host network type. 

From the Docker Docs networking section:

 

Network drivers

 

Docker’s networking subsystem is pluggable, using drivers. Several drivers exist by default, and provide core networking functionality:

• bridge: The default network driver. If you don’t specify a driver, this is the type of network you are creating. Bridge networks are usually used when your applications run in standalone containers that need to communicate. See bridge networks.
• host: For standalone containers, remove network isolation between the container and the Docker host, and use the host’s networking directly. host is only available for swarm services on Docker 17.06 and higher. See use the host network.
• overlay: Overlay networks connect multiple Docker daemons together and enable swarm services to communicate with each other. You can also use overlay networks to facilitate communication between a swarm service and a standalone container, or between two standalone containers on different Docker daemons. This strategy removes the need to do OS-level routing between these containers. See overlay networks.
• macvlan: Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses. Using the macvlan driver is sometimes the best choice when dealing with legacy applications that expect to be directly connected to the physical network, rather than routed through the Docker host’s network stack. See Macvlan networks.
• none: For this container, disable all networking. Usually used in conjunction with a custom network driver. none is not available for swarm services. See disable container networking.
• Network plugins: You can install and use third-party network plugins with Docker. These plugins are available from Docker Hub or from third-party vendors. See the vendor’s documentation for installing and using a given network plugin.

 

Network driver summary

• User-defined bridge networks are best when you need multiple containers to communicate on the same Docker host.
• Host networks are best when the network stack should not be isolated from the Docker host, but you want other aspects of the container to be isolated.
• Overlay networks are best when you need containers running on different Docker hosts to communicate, or when multiple applications work together using swarm services.
• Macvlan networks are best when you are migrating from a VM setup or need your containers to look like physical hosts on your network, each with a unique MAC address.
• Third-party network plugins allow you to integrate Docker with specialized network stacks.

 

Personally, I have my Plex docker container set to host networking as that was the container default and I have no need to change it; however, I have several others on a docker VLAN (br0.3) so they get their own IP address.  I could not use custom IP addresses on custom:br0 without getting macvlan call traces on my server, but the VLAN is fine.

 

Most of my docker containers run in bridge mode.  I usually just stick with whatever the container default is except for those I have moved to br0.3.  I'll probably end up moving more here over time as I keep experimenting.

Thanks @Hoopster, Ok, question for you. Do you segregate your IoT devices? (Your smart TV, Nvidia Shield, ect) from your unRAID server?

 

The easiest thing for me to do it just place my Roku and Smart TV on my Secure LAN but I'm hoping not to. It seems VLANs are maybe more trouble than they are worth. Every application I add (Pi-Hole, Plex) turns into a week long fight with firewall rules, etc. 

 

Thoughts?

3 minutes ago, adminmat said:

Thanks @Hoopster, Ok, question for you. Do you segregate your IoT devices? (Your smart TV, Nvidia Shield, ect) from your unRAID server?

 

The easiest thing for me to do it just place my Roku and Smart TV on my Secure LAN but I'm hoping not to. It seems VLANs are maybe more trouble than they are worth. Every application I add (Pi-Hole, Plex) turns into a week long fight with firewall rules, etc. 

 

Thoughts?

A few day ago, I set up an IoT VLAN but I have not begun moving devices to it.  Right now, I am playing around with WireGuard in the 6.8.0-rcX releases to see how I can get access to br0.3 VLAN docker container webUIs when I am on a remote WireGuard VPN connection.

 

Currently, I have Plex running as host, so, same IP as the unRAID server and my FireTV is on the same LAN subnet.  Obviously, this works without issue.

 

I have a Ubiquiti UniFi USG router and UniFi switches and the default is to route traffic between all subnets if they are defined as "corporate" LANs (Guest networks are isolated).  Of course, firewall rules can restrict that, but, as I am experimenting with VLANs/different subnets, it initially just works.

16 minutes ago, adminmat said:

Every application I add (Pi-Hole, Plex) turns into a week long fight with firewall rules, etc.

I had Pihole running as a docker container, but, I opted to move it to a standalone RPi.  I also have Pihole acting as my DNS when on a remote WireGuard VPN connection. 

 

Port forwarding, dynamic DNS, VLAN/subnet routing, etc. is fairly easy to manage in my router so, fortunately, I have run into very few issues getting things set up properly.  If I complicate things a bit more for security sake (a valid concern), I am sure I would encounter a few more hurdles.

3 minutes ago, Hoopster said:

A few day ago, I set up an IoT VLAN but I have not begun moving devices to it.  Right now, I am playing around with WireGuard in the 6.8.0-rcX releases to see how I can get access to br0.3 VLAN docker container webUIs when I am on a remote WireGuard VPN connection.

 

Currently, I have Plex running as host, so, same IP as the unRAID server and my FireTV is on the same LAN subnet.  Obviously, this works without issue.

 

I have a Ubiquiti UniFi USG router and UniFi switches and the default is to route traffic between all subnets if they are defined as "corporate" LANs (Guest networks are isolated).  Of course, firewall rules can restrict that, but, as I am experimenting with VLANs/different subnets, it initially just works.

 

Well that is a bit more comforting to know others are sharing main LAN subnets with IoT devices. Before I deployed my unRAID server I spent a couple weeks segregating my network. I read so many warnings on why you need to do that it scared me probably more than it should. It was a MASSIVE pain to set up.

 

I haven't even started to do any remote connections (outside of my home) yet. I'm still trying to get things working here. I'm starting to think it's a waste of time to have all these VLANs. The amount of time I've spent on it I could have restored all my data from backups ten times over. 

1 minute ago, Hoopster said:

I had Pihole running as a docker container, but, I opted to move it to a standalone RPi.  I also have Pihole acting as my DNS when on a remote WireGuard VPN connection. 

 

Port forwarding, dynamic DNS, VLAN/subnet routing, etc. is fairly easy to manage in my router so, fortunately, I have run into very few issues getting things set up properly.  If I complicate things a bit more for security sake (a valid concern), I am sure I would encounter a few more hurdles.

Yes, Pi-Hole is also giving me problems on unRAID. When I shut down the server I have to manually go into my router and change the DNS settings for 4 different subnets or I get locked out internet connections. I think having Pi-Hole on a RPi is a much better option. 

 

 

1 hour ago, adminmat said:

When I shut down the server I have to manually go into my router and change the DNS settings for 4 different subnets

Can you specify more than one DNS server on your router?  When I had Pihole in a docker, shutting down the server (as you know) killed Internet on my LAN.  However, since I can specify up to 4 DNS servers on my router, I was able to set Pihole IP as the primary and I had Google and Cloudflare as backups.  When the server was down, the other devices still had Internet as they fell back to a secondary DNS.

 

I prefer the convenience of Pihole on an RPi and still have the same DNS setup as the IP address I had assigned to the Pihole docker is now its IP address on the RPi.

Edited October 18, 20196 yr by Hoopster

24 minutes ago, Hoopster said:

Can you specify more than one DNS server on your router?  When I had Pihole in a docker, shutting down the server (as you know) killed Internet on my LAN.  However, since I can specify up to 4 DNS servers on my router, I was able to set Pihole IP as the primary and I had Google and Cloudfalre as backups.  When the server was down, the other devices still had Internet as they fell back to a secondary DNS.

 

I prefer the convenience of Pihole on an RPi and still have the same DNS setup as the IP address I had assigned to the Pihole docker is now its IP address on the RPi.

I CAN actually specify a 2nd DNS server on my router. I didn't know what that was for! So that's like a failover DNS field? Wow. I'm going to use 8.8.8.8 and do a test. 

 

Edited October 18, 20196 yr by adminmat

Update!  I got it working! This time with much less whining on the forums as usual 😃

It was GDM Network Discovery!! I had to open a destination port range to my Plex server's IP address. Ports 32410 to 32414.

So I'm allowing GDM port range 32410-32414, UDP to my Plex IP address!

I'm allowing 32400 and 8324 also to the Plex IP. 

Thanks @Hoopster for looking at it with me.

 

On 10/18/2019 at 2:24 PM, adminmat said:

Update!  I got it working! This time with much less whining on the forums as usual 😃

It was GDM Network Discovery!! I had to open a destination port range to my Plex server's IP address. Ports 32410 to 32414.

So I'm allowing GDM port range 32410-32414, UDP to my Plex IP address!

I'm allowing 32400 and 8324 also to the Plex IP. 

Thanks @Hoopster for looking at it with me.

 

I am using Unifi but I'm curious if I'm having the same issue. When I setup Plex on a vlan I can launch it from the docker and it works fine. 

I can't access it from any other device on my network. I'm guessing I've overlooked something. When I switch it back to the same IP as unraid, everything works, including remote.