-
Notifications
You must be signed in to change notification settings - Fork 621
FAQ
First step for any issue is to make sure you are running the latest official version (currently version 0.5.0 for desktop and version 0.3.6 for Android and AndroidTV)
There are also other apps using the same name, if your app shows popups or asks for money its not our version. Download the official app or find support for your app on its own forum/site/repo/subreddit.
Popcorn Time is a multi-platform, free software BitTorrent client that includes an integrated media player. It doesn't host any content itself, instead it streams video content through torrents with the content and metadata being provided by various third-party providers/APIs. This basically means that you download small parts of the content from another user's computer, while sending the parts you already downloaded to someone else. Then, you can watch those parts, while the next ones are being downloaded in the background. This exchange allows the content to stay healthy. Once the movie is fully downloaded, you continue to send parts to other users until you stop or remove that torrent, and everything is deleted when you close the app (unless you change the relevant option). As simple as that.
Some ISPs may block the website url. Make sure it's currently online by checking with a service like 'Down for Everyone or Just Me' and if it is the issue is most likely an ISP block. Use a DNS change or a VPN to bypass it.
Find the installer(s) suitable for your Operating System and architecture (32/64bit) then ones with filenames ending in -0.44.5 run on the old NW.js version (0.44.5) while the ones without it run on the new NW.js version (0.82.0). If after narrowing it down using the above there are still multiple available installers you can choose whichever you prefer/works best for you since only the installation method will differ and they will otherwise produce the same result.
NW.js is the application runtime Popcorn Time runs on. Its basically Chromium and Node.js combined so in terms of using this app you can think of Popcorn Time as a big locally hosted website which is where Chromium comes in, its the browser and which also includes a lot of modules doing all the necessary stuff a simple website and a browser couldn't otherwise do and is where Node.js comes in.
A newer version of NW.js means newer Chromium and Node.js versions and all that entails. (you can check their own changelogs for specific changes between versions but like most software the general rule is that newer is better). Adding to that some Operating Systems will have issues even running some versions, either because the OS is new and the NW.js version is too old (e.g the latest macOS versions and version 0.44.5) or because the NW.js version is new and the OS is too old with support for it dropped at some point (e.g Windows 8 and earlier and version 0.82.0). In these instances it comes down to getting the one that supports your OS. Other than this though, the NW.js version they run on, both new and old NW.js builds are the otherwise the same and have the same features, functions and options.
If you've already selected the correct installer(s) as detailed above, try clean installing the app. You can do so by first uninstalling any previous installations then deleting any folders/files that might be left behind. (*you can backup your settings/bookmarks/watched databases and restore them later after the issue is resolved).
Also, for now if you are running a macOS arm build, due to the way they are produced you need to manually remove the quarantine flag by doing xattr -cr /path/to/application.app before running the app. (open issue at #2762)
Try flushing your databases. You can do so from the settings page or by manually deleting the database files. (*if you want you can first backup them then if the issue is resolved selectively restore them until you find what caused it). If the issue isn't resolved by this check the previous section about clean installing. If the above still don't solve the issue check the 'Issues' section of the github repo and if there isn't a relevant issue there, if you want create one with any available information so that others can also try to replicate it and see if its a widespread issue with the app that needs attention.
In the Settings, find the API server section and make sure the API list that popups when you press the relevant field is updated with the latest working API urls. You can do this either by enabling the automatic update, manually updating it, or just adding the urls in. After that just select them and restart the app when prompted. If after doing this you still get a "The remote movies API failed to respond.." error try and open the urls directly in your browser. If they still wont load the issue is most likely an ISP block. Use a DNS change or a VPN to bypass it.
Use the search function in the Torrent Collection tab. You can also copy/paste or drag/drop magnet/torrent links from elsewhere. If it's a series try searching for a full season torrent instead of individual episodes, they are usually better seeded.
If the movie/episode has good health (green health dot) then something is blocking the connection. It might be something locally on your system/network or it might be your ISP in which case you might need a VPN. If you already have a VPN make sure you are connected to a server that supports p2p. If the movie/episode has bad health (red health dot) then use the 'more..' function or the Torrent Collection tab as detailed above. You could also try enabling 'Protocol Encryption' in the settings, it will allow you to connect to more peers (any that also use PE/MSE) but might also result in increased CPU usage and/or UI lag spikes.
If you have already created an OpenSubtitles.org account and connected it to Popcorn Time, and still nothing has subtitles it might be that OpenSubtitles is having issues or doing maintenance. If the issue persists check your connection to their website and REST API urls.
Unfortunately since NW.js doesn't support proprietary codecs and the added available prebuild libraries don't include a few commonly used audio codecs you might run into this issue if using the new NW.js build. (the old version overcomes this by being a custom compiled build using scripts and a process that cant for now be replicated for the new version, open issue at #2062). To overcome this you can use a supported external player (e.g VLC, list of all supported players by pressing the '?' icon in the dropdown menu next to the 'Watch now' button in the app) or find a different video/torrent that the audio will play (e.g change the quality, use the 'more..' function, or the Torrent Collection tab) or ultimately if you just prefer using the build-in player without having to deal with this issue at all use the old NW.js build of the app.
❪*❫ Anyone wanting to add/edit a Wiki page please notify someone with access (e.g a collaborator) to unlock it for you.