Rauno Tegelmann

@EricHupp Looks like there's actually 2 errors going on here at once. Could you please try to alter your `.env` as follows: ``` NEXT_PUBLIC_OVERSEERR_URL=http://192.168.1.99:5055 PLEX_HOSTNAME=localhost ``` It might also help...

@EricH9958 The sharp error should be fixed in `1.8.7`. Please try updating and let me know how it works. However, I'm guessing that you will still get the same error,...

@SiskoUrso Thanks for reporting and the detailed logs. @EricH9958 and @SiskoUrso are the errors only appearing in `/rewind` or also `/dashboard`?

If you can, please help me debug the issue further: 1. Get the [debug/missing-user-id](https://github.com/RaunoT/plex-rewind/tree/debug/missing-user-id) branch. I have added additional debugging steps there to help troubleshoot. Let me know if you...

@SiskoUrso Thanks! The scrubbing is fine, can you please confirm if the ID is the same in all the logs?

Hello again 👋 I've just published a `2.0.0` version of `plex-rewind`. Since this issue deals with parts of the code that have been completely refactored, I will close this issue...

I think we'll also need to create some sort of config screen to allow the admin to set the values that are currently set in the `.env` file. Wondering regarding...

Unsure how to handle SSR, generateStaticParams and other build optimizations when using a published (built) Docker image. We need to have the relevant API keys etc. at build time for...

> Could you add a "latest" tagged Docker image? Most applications dealing with Docker containers assume "latest" if a specific tag isn't provided. Good point, re-opening this.

:tada: This issue has been resolved in version 2.0.0 :tada: The release is available on: - [GitHub release](https://github.com/RaunoT/plex-rewind/releases/tag/v2.0.0) - `v2.0.0` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket: