Contents
On this page

Troubleshooting - Plugixa Stream

This page lists the problems people meet most, what causes each one, and how to fix it. Start with the section that matches what you see.

Most of them come down to one of three things: the Watch page, the WordPress REST API, or the address of the video file. The Watch app loads everything (the home screen, series, episodes and resume points) from the REST API under /wp-json/plugixa-stream/v1/, so anything that blocks it stops the app.

The Watch page is missing or shows a 404

The Watch app lives on one WordPress page that holds the [plugixa_stream_app] shortcode. On activation the plugin creates a published page called Watch at /watch/, unless a page with the shortcode already exists.

  1. Open Plugixa Stream -> Settings -> General and look at Watch page.
  2. If the page was deleted, unpublished or renamed, create a page, add the [plugixa_stream_app] shortcode to it, publish it, and select it under Watch page.
  3. Click Save.

Links from series pages, embeds and emails follow the page chosen here. See Watch app.

Series and episode pages show a 404

Series pages live at /series/<name>/, episodes at /episode/<name>/, the browse page at /series/ and genre pages at /series-genres/<name>/. If these return “Page not found” while the Watch app works, WordPress’s address rules are out of date. Open Settings -> Permalinks in WordPress and click Save Changes without changing anything. See SEO.

The Watch page does not look like the rest of my site

That is on purpose. The Watch page is shown full screen without your theme’s header, footer, sidebar or stylesheets, so the player can fill the screen. Its colours, font and logo come from Settings -> Appearance; see Appearance.

A theme can still take over the page by shipping its own plugixa-stream-app.php template. To show titles inside your theme’s normal pages, use the shortcodes or blocks instead.

The app says “Something went wrong loading this page.”

The app could not reach the REST API. Open this address in a private browser window, with your own domain:

https://example.com/wp-json/plugixa-stream/v1/home

You should see text starting with {"success":true. If you see an error, a login page or a “REST API disabled” message instead, something blocks the API for visitors:

  • A security plugin with an option such as “Disable REST API” or “REST API for logged-in users only”. Allow the plugixa-stream/v1 routes, or switch the option off.
  • A firewall or host rule that blocks /wp-json/. Ask your host to allow it.

The app also needs JavaScript. Without it, visitors see Please enable JavaScript to watch.

An episode does not play

When an episode cannot start, the player shows This episode could not be played. with a Try again button. Open the episode in the admin and check its video source first. See Video sources.

Cause What to check
No video is set An episode without a source answers “This episode has no video yet.” Pick a file from the Media Library or enter its address.
The address is wrong Open the video address in a new browser tab. It must play or download there first.
Mixed content Your site uses https:// but the video address starts with http://. Browsers block it. Use an https:// address.
The file’s format Browsers play MP4 files with H.264 video and AAC audio everywhere. Other codecs, such as HEVC, play only in some browsers. Re-export the file as H.264 MP4, or, with Pro, use an HLS playlist (.m3u8).
HLS on another domain PRO Chrome, Firefox and Edge load HLS playlists and segments through JavaScript, which the other server must allow with a CORS header (Access-Control-Allow-Origin). Safari plays HLS natively and may work while other browsers fail. Add the header on the server that hosts the files.
The series is a draft An episode of a draft series answers as if it did not exist. Publish the series.

A YouTube or Vimeo episode does not play

Embed addresses must start with https://. The plugin recognises these links and turns them into the player each service allows on other sites:

  • YouTube: youtube.com/watch?v=..., youtu.be/... and /shorts/, /live/ and /embed/ links.
  • Vimeo: vimeo.com/123456, an unlisted vimeo.com/123456/abcdef link, and player.vimeo.com/video/123456.

Any other https:// address is loaded as it is, in a frame. Use the host’s embed address, not the address of its watch page: most sites refuse to be shown in a frame from their watch page.

If the address is right and the video still does not play, the video’s owner may block it:

  • On YouTube, the video must allow embedding.
  • On Vimeo, a video limited to some domains must list your site’s domain under its embed privacy settings.

Progress or My List is not saved

Guests: resume points stay in their own browser only, so they do not follow them to another device, and a private window forgets them. They are carried into the account when the guest signs in. My List and likes need an account.

Signed-in viewers: the app saves the position every 10 seconds and again when the tab is hidden or closed. If positions do not come back:

  • The REST API is blocked for signed-in users. Check it as described in Something went wrong loading this page.
  • The Watch page is cached for signed-in viewers. Each save carries a security token (nonce) printed on the page. A page served from a cache carries an old token, and WordPress refuses the save. The plugin asks caching plugins not to cache the Watch page for signed-in viewers (DONOTCACHEPAGE). If your cache ignores that, exclude the Watch page, or signed-in users, from it.
  • The episode is locked for this viewer. Positions on an episode the viewer may not play are ignored.

See Resume and My List.

Too many requests

To slow down bots, the plugin allows 60 requests a minute per viewer on the routes worth scraping: starting an episode, and with Pro PRO unlocking with coins, claiming rewards, checking a coupon, writing or reporting a review and managing screens. Above that, the request is refused with “Too many requests. Please wait a moment and try again.” A person swiping through episodes stays far below it.

Signed-in viewers are counted per account; guests per IP address (hashed, never stored).

If many guests are refused at once, your site is probably behind a proxy or CDN that hides the visitors’ real addresses, so every guest arrives with the proxy’s address and shares one counter. Make the server see the real visitor address (most hosts and CDNs document a setting or module for it), or raise the limit with the plugixa_stream_rate_limit filter:

add_filter( 'plugixa_stream_rate_limit', function ( int $limit, string $bucket ) {
	return 'play' === $bucket ? 240 : $limit;
}, 10, 2 );

Returning 0 switches the limit off for that bucket. See Hooks.

“Two copies of Plugixa Stream are active”

Pro is a separate plugin. When the free copy and the Pro copy are both active (for example after activating Pro from WP-CLI or a hosting panel), only the copy that loads first runs. The other one stops before doing anything, and administrators see a notice that names the copy that was not loaded.

Nothing is lost: both copies use the same series, episodes, viewer data and settings. Open Plugins, deactivate the copy you no longer need (usually the free one), and delete it if you like.

Deleting a copy never erases content while another copy is still installed, even with Delete all data on. See Privacy and uninstall.

“Plugixa Stream could not finish setting up its database”

This notice appears when the plugin could not create one of its tables. It names each table and the database’s answer. The usual cause is a database user that is not allowed to create tables. Ask your host to grant that permission, then click Try again in the notice.

Genre pages are empty with Polylang

Polylang filters genre, tag, studio and language pages by language. The plugin lifts that filter for its own pages, so they show every title, as long as the Stream series type is not set as translatable in Polylang’s settings. If you made it translatable there, Polylang’s filter is kept, so give each series a language. See Multilingual.

Pro features

Problems with a Pro feature are covered on its own page: Encoding (ffmpeg not found), Bunny Stream, Stripe and PayPal (webhooks), and Video ads.

Quick Links

Share