If i try to connect from outside, i have access to the flexTV web ui. With port 1778 forwarded in my router to 1778 of my local ip of my hassio server where the FlexTV addon is install… In “setting” in the web ui of PlexTV, i try to put my external Ip, forward in my router : Nothing more…dont understand what i am doing wrong? The Log in the addon stop after "starting NGinx" The strange thing is i have any log in FlexTV web browser… If i ask my google home, i have the response that he dont understand what i m asking for : “ok google, talk to FlexTv”. Webtools help you organize Plex media content. Then i can see my android Tv or my firefox cast, but when i write “play something” nothing append. Project recently migrated from gitlab to github to improve development flow (docker builds and binary releases). When i open the Web Ui of FlexTV, it open, i click “Do It” then i link my Google account for Plex sucessfully. I can reach my Plex server from outside with, UPNP is on in my router so port forwarding to 32400 of the local IP of my Plex server. I have already NGinx Addon, dont know if its the problem or not? (i try put off,no change). I have then install the Addon FlexTV on hassio on my RPI4. I have my Plex server, work great, on docker, on my NAS, omv5. Should we thus leave it in a _disabled_ state (greyed out) or simply hide it? I would tend to lean on the former, as it would provide further indication to the user that the Rock-on does have a webUI and that changes to the ports were made.I have read the docs and i am on it for a few days now, so i ask some help because it doesnt work : If the webUI port (if applicable) is unpublished, the webUI button displayed in the Rock-ons summary page would not work anymore. Plex WebTools is a plugin for Plex that allows installation of extra modules including subtitle management. Should we offer the possibility to edit the container port as well (or leave this for a future and separate issue/PR)?ģ. let user choose to not expose the port (if desired) via checkbox (such checkbox would be checked by default)Ģ. If one chooses to unpublish a port, I can see three possibilities: Now, you shall be redirected to another page > Click on the ‘Clone or Download’ option > finally, select to download the zip file. After opening the link click on the Plex channels, you wish to install. In the future, we may work on adding the possibility to create the network from here, as an enhancement.ġ. Open your device and go to the Plex Forum or from another source, which has a variety of Plex plugins for you to choose from. WebTools-NG 4 Plex has 3 repositories available. server, in building up a new unRAID box and installing Emby via Docker. manual Public WebTools-NG Manual 1 CC0-1.0 0 1 0 Updated on Aug 18 WebTools-NG Public WebTools Next Generation for Plex JavaScript 558 MPL-2.0 21 53 6 Updated on Feb 24 testman Public TestMan 0 MPL-2.0 0 0 0 Updated on Jan 2 WebTools NG is Next Generation of WebTools 4 Plex. On the next step (or below this one), one may attach the Rock-on's container(s) to one or more pre-existing docker networks. Plex Media Server to help you better enjoy movies with Plex media server. This could be implemented on the Rock-on customization dialog next to the other customization options currently existing (see below).Ĭlicking on the "Ports" button would lead to a dialog to edit all ports: Restart the application and upgrade to the latest version: docker restart plex. See the logs given by the startup script in real time: docker logs -f plex. > I would actually like to see an option to export or not the ports in the GUI, _then_ we would have a use for network creation and joining.Īs a result, we can offer an advanced post-install customization option to advanced users to un-publish predefined ports and then join docker networks of interest. Shell access to the container while it is running: docker exec -it plex /bin/bash. Indeed, as described by in the issue referenced above (), joining a docker network would be useful/required only if predefined ports are not published: In order to make custom docker networks (described in #2009) useful, we need to create an interface to edit the ports described in a Rock-on JSON file. It is meant as tracking and discussion material for a work currently **in progress**. This issue relates to step 3 of Rock-ons networking work described in #1982, and … follows steps 1 (#2003) and 2 (#2009).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |