How do you keep track of all of the ports used in unRAID

[wayner]

I am just starting to add a few dockers and one thing that is becoming apparent is that you have to be careful so that you don't have multiple dockers trying to use the same ports.

So far I have added SageTV, AirVideoHD, Dockergui-dev, Dolphin, Home-Automation Bridge and Plex.

At least one of these dockers wanted to use 8080 but I am already using that for the Sage Jetty webserver.

When you click Show deployed host ports it shows some, but not all of the ports that are being used. For example it doesn't show the port that Plex is using, which is at least 32400 for the web UI and probably others for streaming if I remember correctly. Nor does it show that HA-bridge is using 3080.

Going to a command line and typing "lsof -Pni |grep LISTEN" does show a list but is there any way to do this in a more organized fashion fro the web GUI?

[Fuzzy]

unRAID needs to be told what ports a given container uses. This is done in the template/docker settings. It does not, however, monitor what ports are opened up by each docker - it's just if a container tries to open up a port that is already open, it will fail.

Show deployed host ports will show what ports are configured for each container.

So really, it comes down to the creator of the template to make sure the right ports are indicated. The plex container I'm using DOES list 32400 as the port used (which really IS the only listening port used by plex).

[wayner]

Originally Posted by Fuzzy

The plex container I'm using DOES list 32400 as the port used (which really IS the only listening port used by plex).

Any opinion on which is the best Plex docker to use. There must be at least 5 that are called Plex or Plex Media Server, plus many other related ones.

[KarylFStein]

If there's one by "linuxserver" I've found their things to be good and supported. But I don't have a ton of experience with dockers.

[stuckless]

Originally Posted by KarylFStein

If there's one by "linuxserver" I've found their things to be good and supported. But I don't have a ton of experience with dockers.

I tend to use the linuxserver.io dockers as well.

[stanger89]

Originally Posted by Fuzzy

unRAID needs to be told what ports a given container uses. This is done in the template/docker settings. It does not, however, monitor what ports are opened up by each docker - it's just if a container tries to open up a port that is already open, it will fail.

Show deployed host ports will show what ports are configured for each container.

So really, it comes down to the creator of the template to make sure the right ports are indicated. The plex container I'm using DOES list 32400 as the port used (which really IS the only listening port used by plex).

I was under the impression (and maybe this is what you're saying) that Docker inbound ports only "work" if you specify them when you start the container:
https://docs.docker.com/engine/userg...twork/binding/

In other words I thought that if the template didn't specify 8080, you wouldn't be able to connect to that container on that port from the outside world, even if something inside the container was trying to listen on it.

[EnterNoEscape]

Originally Posted by stanger89

I was under the impression (and maybe this is what you're saying) that Docker inbound ports only "work" if you specify them when you start the container:
https://docs.docker.com/engine/userg...twork/binding/

In other words I thought that if the template didn't specify 8080, you wouldn't be able to connect to that container on that port from the outside world, even if something inside the container was trying to listen on it.

That's only if the container isn't running in host mode.

[stuckless]

Originally Posted by stanger89

I was under the impression (and maybe this is what you're saying) that Docker inbound ports only "work" if you specify them when you start the container:
https://docs.docker.com/engine/userg...twork/binding/

In other words I thought that if the template didn't specify 8080, you wouldn't be able to connect to that container on that port from the outside world, even if something inside the container was trying to listen on it.

That is true if you are running in bridged mode...but in host mode (which most things shouldn't run in), the container can open as many ports as needed.

SageTV runs in host mode.. so it uses 8080. Running sagetv in bridged more makes it appear as if it is "remote" to the netowk, so even local LAN clients get the placeshifter login.

[Taddeusz]

Originally Posted by wayner

Any opinion on which is the best Plex docker to use. There must be at least 5 that are called Plex or Plex Media Server, plus many other related ones.

Plex has their own Docker now. It is available as PMS-Docker.

[KarylFStein]

Originally Posted by Taddeusz

Plex has their own Docker now. It is available as PMS-Docker.

I hear it's pretty temperamental, lol.

[Taddeusz]

Originally Posted by KarylFStein

I hear it's pretty temperamental, lol.

In what way? I've not had any trouble since moving to it.

I was running the linuxserver.io one for only a short time. But I can say that the Lime Technology Plex docker is not great. Apparently they have to manually update the docker every time there's a new PMS version and the lag is sometimes not acceptable.

[EnterNoEscape]

Originally Posted by Taddeusz

In what way? I've not had any trouble since moving to it.

I was running the linuxserver.io one for only a short time. But I can say that the Lime Technology Plex docker is not great. Apparently they have to manually update the docker every time there's a new PMS version and the lag is sometimes not acceptable.

I believe it was intended to be a joke. While the acronym is accurate for the software title. I still think they could have chosen more wisely or just picked a different name all together.

[Taddeusz]

Originally Posted by EnterNoEscape

I believe it was intended to be a joke. While the acronym is accurate for the software title. I still think they could have chosen more wisely or just picked a different name all together.

Oh, duh.

[Fuzzy]

I was using the limetech plex template - just installing the plexinc one now - we'll see how it goes.

[stanger89]

Tangentially related....

One of my Dockers is Logitech Media Server, which so far has worked great. However I discovered there's a built in UPnP/DLNA server, so I was trying to get it to work. The Docker is setup in bridged mode with a number of ports exposed by default (TCP: 3483, 9000, 9090, UDP: 3483).

Through my research, I found a number of ports listed that need to (UDP: 1900, 1901, 2698; TCP: 50001, 50002), so I tried adding those to the container, however nothing would see it as a DLNA server. 1900 is supposedly the key port, as that's for SSDP discovery.

As a last stitch effort, I changed the container over to Host mode networking and it showed right up to DLNA clients. So the question is, anyone have any ideas how to either find whatever ports are missing, or if there's some other configuration I need to do to get it to work in Bridge mode?

[wayner]

Maybe you could do a port scan from within the docker on localhost using something like nmap? Perhaps that could work.

I just realized an additional issue with Sage if you are running other plugins like SageTCPServer as it uses a whole whack of additional ports.

[KarylFStein]

Originally Posted by stanger89

Tangentially related....

One of my Dockers is Logitech Media Server, which so far has worked great. However I discovered there's a built in UPnP/DLNA server, so I was trying to get it to work. The Docker is setup in bridged mode with a number of ports exposed by default (TCP: 3483, 9000, 9090, UDP: 3483).

Through my research, I found a number of ports listed that need to (UDP: 1900, 1901, 2698; TCP: 50001, 50002), so I tried adding those to the container, however nothing would see it as a DLNA server. 1900 is supposedly the key port, as that's for SSDP discovery.

As a last stitch effort, I changed the container over to Host mode networking and it showed right up to DLNA clients. So the question is, anyone have any ideas how to either find whatever ports are missing, or if there's some other configuration I need to do to get it to work in Bridge mode?

The discovery uses a multicast IP and I'm guessing unRAID won't act as a network translator for the containers.

[Fuzzy]

Originally Posted by KarylFStein

The discovery uses a multicast IP and I'm guessing unRAID won't act as a network translator for the containers.

This is correct, and is the reason sage is also run in host mode. UDP broadcasts are not sent to the docker subnet.

[stanger89]

Well, that makes sense I guess. Turns out the functionality is kind of useless to me anyway, as playlists aren't exposed by the LMS UPnP server.

[Fuzzy]

Originally Posted by stanger89

Well, that makes sense I guess. Turns out the functionality is kind of useless to me anyway, as playlists aren't exposed by the LMS UPnP server.

What are you trying to do with LMS over UPnP?