FAQs - SpaceK33z/web-to-plex GitHub Wiki

What do I need to use Web to Plex?

You will need:

  • Google Chrome ("Chromium" on *nix machines)
  • Mozilla Firefox
  • Microsoft Edge (Chromium version)
  • Opera (Chromium version)
    • Safari (Chromium version) support is projected for 2020 or later (if it isn't just a rumor)
  • A valid Plex account and functioning server (recommended)
  • At least one valid NZB media manager (recommended):

I can't find my Plex token, what should I do?

Please read Finding an authentication token / X-Plex-Token, explaining where and how you can find a Plex token.

If you still can't seem to find your Plex token, then please use an alternative method under Login | Login Settings.

Please note that your credentials won't be saved, only your Plex token.

Why isn't the extension working?

Please be sure to fill out the options page and press the save button at the end of the page.

I filled out the options, but it still doesn't work (Mixed Content Error)

For the URLs you've entered, be sure to include HTTPS (if you're allowed) and not HTTP. If you're not allowed to use HTTPS, then please enable the Force Secure Connections option under Connection Settings | Proxy Settings.

I filled out the options, but it still doesn't work (Firefox/Safari)

Please be sure you're using the stable version from your extension store, or directly from SpaceK33z. If you're using the version from Ephellon then you're using the unstable version meant for testing on Chrome only.

Why does the extension ask for permission to change site data?

This is used in order to add the Web to Plex button to the site.

For Couchpotato users, this is also used to communicate with Couchpotato (as it requires content embedding).

What about my privacy? How are my credentials used/stored?

Privacy Policy: Your credentials are used only to communicate with the respective service (i.e. your Couchpotato credentials won't be sent to Watcher 3, only to Couchpotato).

When sending a request to a service, Basic Access Authorization will be used.

Your credentials are stored according to your browser's settings:

  • Chrome/Chromium: remotely (if enabled) on Google's password servers, and/or locally (on your device)
  • Opera: remotely (if enabled) on Opera's password servers, and/or locally (on your device)
  • Firefox: remotely (if enabled) on Mozilla's password servers, and/or locally (on your device)
  • Safari: remotely (if enabled) on Apple's password servers, and/or locally (on your device)
  • Edge: remotely (if enabled) on Microsoft's password servers, and/or locally (on your device)

More information on how your credentials are stored can be found in your browser's settings.

Why does the extension want access to all sites?

This permission is used to communicate with HTTPS served pages. In latent terms, if you want to use https://localhost:32400 (Plex), the extension needs permission to communicate with https://localhost. By accessing all URLs, sites can be added much easier, without having to send multiple prompts for access to the same site (i.e. HTTPS v. HTTP served pages).

Why is Plex It! on GitHub and not built in?

This is for easing maintenance. Instead of releasing new versions of Web to Plex every time Plex It! changes, it can simply be hosted here and changed seamlessly.

Why is Plex It! running so slow?

This could be one of many things, but we recommend white-listing https://ephellon.github.io/, http://localhost/ and https://localhost/ in your AdBlocker's settings (there aren't any ads, so it's running for no reason).

Can I use the extension outside of my browser?

No. The extension runs entirely within your browser, on your device. The extension only communicates with your NZB manager(s), the supported sites, GitHub (this site) if enabled, and the store (where you installed the extension) for updates.

On Apple devices (running Safari), although an external application is used to install the extension, there aren't any external scripts used by this application.

What data is sent to sites I visit?

Sites (other than Plex It!) are never sent any data from this extension. The site's code is modified with a finished button that contains a URL to Plex (if the item is found), or just a button with IDs that the extension uses later.

Plex It! is sent the same information above, as well as the item's image (if available) once the "add to Plex It!" button is pressed by the user.

What if I visit a site that's not on the supported list?

Sites not approved for full implementation can be found under the Site Settings | Experimental Sites section of the options page. If the site isn't on that list or the Default Sites' list, Web to Plex doesn't bother running.

Sites that are on the experimental list must be enabled by the user before they will work.