-
Notifications
You must be signed in to change notification settings - Fork 18
FAQs
You will need:
- Google Chrome, Google Chromium (*nix machines), or Mozilla Firefox.
- A valid Plex account and functioning server.
- At least one valid NZB media manager (recommended):
Plex offers a detailed guide, explaining where and how you can find your Plex token.
If you still can't seem to find your plex token, then please use an alternative method under Web to Plex Options | Plex Settings | Login | Login Settings.
Please note that your credentials won't be saved, only your Plex token.
Please be sure to fill out the options page and press the save button at the end of the page.
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 in the Advance settings.
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.
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).
Your credentials are used only to communicate with that 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, or locally (on your device)
- Firefox: locally (on your device)
More information on how your credentials are stored can be found in your browser's settings.
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.
This is for easing maintenance. Instead of releasing new versions of Web to Plex everytime Plex It! changes, it can simply be hosted here and changed seamlessly.
This could be one of many things, but we recommend whitelisting 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).
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.
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.
Sites not approved for full implementation can be found under the Advance Settings section of the options page. If the site isn't on that list either, Web to Plex doesn't bother running on that site.
Sites that are on this second list must be enabled by the user before they will work.
If you want to request a feature, please make an issue and add "Feature" to the beginning of the title (e.g. "Feature: Support XYZ.com").
If you want to report a bug/problem, please make an issue.
If you want to request a feature, please submit a Feature request.
If you're having some trouble with the extension, please see the Wiki.
If you want to report a bug/problem, please submit:
- a Bug Report for generic errors that can be easily fixed (e.g. a website updated, the scripts are outdated; or, the extension no longer works on a site)
- a Fail Report for errors that make the extension unusable (e.g. can't save settings)