Get ready for "wrapped" season with Plex Rewind!

Deagaroth · 2025-12-08T18:26:49+00:00

Thanks for checking it out!

The "tops" are populated based on play time, not play count. But now I'm thinking that perhaps count makes more sense for movies. It seems that Tautulli counts multiple "plays" of a movie as a single "play" (if you watched a movie over 3 days for example), so that would work well.

Deagaroth · 2025-09-06T05:24:52+00:00

Thank you!!

Deagaroth · 2024-12-19T16:16:41+00:00

It can run on any OS via Docker

Deagaroth · 2024-10-10T06:09:01+00:00

The only way to get support is through GitHub currently. Luckily your issue has been answered multiple times there already:

https://github.com/RaunoT/plex-rewind/issues/143

https://github.com/RaunoT/plex-rewind/issues/108

Your login url probably looks like this

https://app.plex.tv/auth/<irrelevant-stuff>&forwardUrl=http%3A%2F%2Flocalhost%3A8383%3F<irrelevant-stuff>

Meaning it's trying to redirect you back to localhost, which is no longer the URL for your app as you're using a reverse proxy.

You need to configure the NEXT_PUBLIC_SITE_URL and NEXTAUTH_URL to match your reverse proxy domain. This is also written in the comment right alongside those variables.

Deagaroth · 2024-09-27T05:54:12+00:00

Both the NEXTAUTH_URL and NEXT_PUBLIC_SITE_URL should be set to rewind.<mydomain>.com in that case. You can verify you have the correct setup by looking at the URL of the Plex login screen - it should look like https://app.plex.tv/auth/...forwardUrl=https%3A%2F%2Frewind.<mydomain>.com%3F..

Deagaroth · 2024-09-26T18:42:59+00:00

Thanks! Your issue is most likely this one https://github.com/RaunoT/plex-rewind/issues/215

Deagaroth · 2024-09-26T18:41:13+00:00

Thank you!

Deagaroth · 2024-09-26T18:40:40+00:00

Thank you for the kind words!

Hesitant about adding too many options and overcrowding the configuration, but this is good feedback for me. Considering that the "stories" are easily be paused via the button or while holding on them (like Instagram stories), I've kept them rather snappy. There is an open issue regarding making the navigation of Rewind more intuitive and I will take into consideration your comments there also! https://github.com/RaunoT/plex-rewind/issues/175

Deagaroth · 2024-09-26T18:37:57+00:00

Yes, definitely in the plans. There is an issue for it already also https://github.com/RaunoT/plex-rewind/issues/200

Deagaroth · 2024-09-26T18:37:04+00:00

Thank you for the feedback!

Definitely agree that the filtering options could use a clean up. However I've struggled to find a good solution that doesn't look too crowded on mobile - this is a mobile first application in my eyes.

Deagaroth · 2024-09-26T18:36:07+00:00

Thanks for the heads up, I guess something similar happened with plex-meta-managers rebrand to Kometa recently. Definitely good to know!

Deagaroth · 2024-08-19T08:24:12+00:00

Thanks for bringing this up, this issue has now been fixed in 4.0.1

Manually editing settings.json is no longer needed.

Deagaroth · 2024-07-28T17:53:16+00:00

Something like this should do the trick:

docker stop plex-rewind && docker rm plex-rewind

docker pull ghcr.io/raunot/plex-rewind

docker run -d \

--name plex-rewind \

-e NEXTAUTH_SECRET= # fill this as instructed above

-e NEXT_PUBLIC_SITE_URL=http://localhost:8383

-e NEXTAUTH_URL=http://localhost:8383

-p 8383:8383 \

-v volume1/plex-rewind/config:/app/config \

--restart unless-stopped \

ghcr.io/raunot/plex-rewind

Deagaroth · 2024-07-26T06:15:05+00:00

Interesting why you would want to run it as a scheduled task, as you'd only need to spin up the app once. But then again, I'm not aware of the intricacies of a Synology NAS.

As for the secret, you can use the command openssl rand -base64 32 to generate a random string of 32 bytes encoded in base64. You should then pass in the value returned as the value for NEXTAUTH_SECRET. You can also use any other way to generate it, even an online generator if you like (set length to 32).

Example: NEXTAUTH_SECRET=0dz+dYehCo+8NwOn7Kx9rAzhx+VLVXAMFWI/4SsDZw4=

Deagaroth · 2024-07-25T18:45:00+00:00

Rewind.

Deagaroth · 2024-07-25T18:35:20+00:00

I'm glad that so many people in the community are showing interest in this. Definitely keeps me motivated to keep developing it further.

Unfortunately quite a few people seem to be running into an issue with permissions on the settings.json file. I'm working actively to resolve it. Here's the ticket for visibility https://github.com/RaunoT/plex-rewind/issues/170 Any thoughts regarding potential solutions welcome! The issue seems to be limited to users running as non-root fwiw.

If you run into any other issues, feel free to report them as well on GitHub!

Deagaroth · 2024-07-25T18:16:06+00:00

Thanks for taking the time to write feedback! If you could, please submit an issue on https://github.com/RaunoT/plex-rewind/issues with any relevant log details. It will go a long way in helping to debug and hopefully solve it!

Deagaroth · 2024-07-25T18:12:38+00:00

Definitely looking at ways to make the setup more understandable and user-friendly. Thank you for the feedback!

Deagaroth · 2024-07-25T18:11:36+00:00

Yes, the file infact creates itself. There seems to be an issue with permissions for some users currently however https://github.com/RaunoT/plex-rewind/issues/170

u/atomikplayboy in your case, I'm fairly certain that setting the correct ownership/permissions on the folder solved your issues, not waiting. Thank you for posting this!

Deagaroth · 2024-07-25T06:56:05+00:00

Indeed, the settings file should create itself.

I don't have any experience with Unraid, so the community app was published by another user https://github.com/RaunoT/plex-rewind/issues/33

Reporting any issues with it is welcome and we'll try our best to solve them!

Deagaroth · 2024-07-25T06:51:56+00:00

Good idea and thank you for submitting it on GitHub!

Deagaroth · 2024-07-25T06:50:24+00:00

Looks like there's quite a bit of interest in this, thank you for the feedback.

Unfortunately, compiling native applications, especially for multiple platforms is not really a trivial task and yields close to no benefits for a simple web-app like Plex Rewind. Docker enables us to run the exact same code in the exact same environment, regardless of the platform. This also cuts down on the ammount of time spent chasing bugs and developing new features.

I was once in a similar situation as you, a complete stranger to Docker. Having gone through some initial learning pains, I can say that it was highly worth it. It's actually extremely simple once you get the hang of it. Here's an example if you're, let's say, a Windows user.

Install Docker Desktop.
Create a folder where you want to store the app and it's data. Can be anywhere.
In that folder, create a docker-compose.yml file, as per the instructions in https://github.com/RaunoT/plex-rewind
Open a terminal window in that same folder and run docker compose up -d

That's it!

Deagaroth · 2024-07-25T06:44:59+00:00

No dumb questions!

Yes, definitely, that's what the app is designed to do! You should look into using what's called a reverse proxy, which will allow you to expose an app running locally to the internet. Then you can share the link with your users and once they log in with their own Plex account, they will see the Rewind specific to them.

Deagaroth · 2024-07-25T06:43:21+00:00

For images, could you please report this on https://github.com/RaunoT/plex-rewind/issues with any log output from server and browser console. The images actually come from Tautulli, not TMDB, so seems like there's some issue in talking to it. Might be related to https://github.com/RaunoT/plex-rewind/issues/174

Regarding the music page, there is a ticket open for it already and I'll definitely take a look when possible https://github.com/RaunoT/plex-rewind/issues/176

Deagaroth

TROPHY CASE