Slinkynose
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Slinkynose
-
-
Thank you Squid. I've seen this reply on many threads with port questions. I thought it only applied when in host mode. The Plex docker does have its own IP on the proxynet subnet. 172.18.0.4.
As a general question though, why am I not able to add a new port mapping to a container? The config page let's me create and apply, but it doesn't actually apply?
Maybe I am barking up the wrong tree for why Webtools is inaccessible, and I will post in the Plex container forum.
-
I have the Linuxserver Plex docker running on the Custom:proxynet network type based on the SpaceInvaderOne tutorial.
I am trying to add another port (33400 for Webtools), but it doesn't seem to save when I apply the settings and restart the container. It doesn't show up in the port mappings list.
Any ideas?
-
I am also having this issue, and if I add a new port mapping it doesn't show up. It's like Docker is no longer applying my port changes. FYI, I am on the custom bridge: Proxynet, as I followed SpaceInvaderOne's tutorial.
[Plex Docker Help] WebTools & Unsupported App Store
in Docker Engine
Posted
I am also having a problem opening the web page. From all the logs, WebTools appears to start correctly.
I run the Plex docker on the Custom:Proxynet network type, and have tried to add 33400 as an additional port mapping in the docker. It doesn't seem to work.
Any ideas?