Once you have dizqueTV running and have accessed the web ui, go to the Settings link.

• In the Settings page select Plex.
• Click Sign in/Add Servers button.
• The web browser most likely blocked a popup from opening. Unlock the popup and login to plex.
• After approving the plugin in Plex, go back to dizquetv's ui and wait for the server to appear.
• Once your server appears listed and has displays the status of both UI and Backend route as Ok, you can continue to the next step.

Troubleshooting

Backend/UI route error

• The "backend route" is the connection the dizqueTV server to the Plex server. If you are running them both in the same machine, then this is usually a trivial connection. But if the Plex server is remote or if Plex and/or dizqueTV are running in docker, it's no longer as easy. If this connection fail,s it will mean that dizqueTV won't be able to play videos from that Plex server.

• The "UI route" is the connection from the web browser instance you are currently using to run the dizqueTV Web UI to plex. If this fails, it means you won't be able to browse the Plex library using the dizqueTV web UI in your current desktop computer. This issue usually manifests as an empty Plex library when attempting to add programs.

When connecting your Plex account to dizqueTV, it will try to find all servers that can be reached correctly both from the backend and the UI. But if it doesn't find any such server, it will add one that has one problem with the routes. You will have to fix the connection issues manually or to edit the Plex server configuration in the dizqueTV UI to point to a correct server url.

Finding a plex address and token that works for you

You can use this guide: https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/ . Just note that the guide talks about how to find a token. But this time you are most interested in the address. The plex address will appear in the browser address bar (before the token) when you follow that guide.

Docker

Docker can make the resolution of this issue particularly difficult because the same address needs to work both from the UI and the backend. But the backend is going to be a container and the UI is going to run on your host computer. A really quick fix is to spoof the plex server address X-Y-Z-W.blahblahblahblah.plex.direct in docker as a fake hostname that directs to the correct IP to use from docker. This can be accomplished by using the --add-hosts parameter in the docker run command, or its equivalent (docker-compose, unraid, portainer, etc; each have their own way to specify a custom hostname)

Routes were working correctly, but suddenly they broke?

There are two possible explanations for this

Plex token has expired

It's possible that the token that was detected when setting up the plex server has expired. Plex tokens can even be suspended manually from Plex settings. This will materialize as Status Code 401 errors in the dizqueTV logs when playing videos with ffmpeg logging enabled. In this case, use the guid: https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/ to find a working Plex token, and replace it in the dizqueTV Plex configuration (edit the plex server).

Plex server address has changed

There are reports of this happening occasionally when the server hosting the plex instance gets a full reboot. Use the instructions above to find a good server address.