chrisryn/requestarr
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

feat: Overseerr to Jellyseerr migration (#2019)

Browse Source 
* feat: add Overseerr migration

* refactor: rename to Seerr

* refactor: more rename to Seerr

* feat: update the value of the MediaStatus.DELETED enum

* fix: add more details in migration logs

* fix: replace .update by .save for TypeORM hooks

* fix: add fake migration to skip the duplicated UpdateWebPush migration

* fix: rewrite the AddUserAvatarCacheFields migration for Overseerr merge

* fix: replace jellyseerr migrations with a dedicated one for overseerr

* fix: update overseerr migration

* fix: update overseerr migration

* fix: remove irrelevant changes

* fix: typos

* docs: update jsdoc comment

* docs: update seerr description

* docs: fix the contributing.md link

* fix: remove unwanterd change on postgres dev datasource

* docs: add latest tag to docker image

* fix: migrate old deleted status for 4k media

* fix: update Seerr version check
This commit is contained in:
Gauthier
2025-10-30 19:57:50 +01:00
committed by GitHub
parent 2e6e9ad657
commit 4e9c94c80f
60 changed files with 942 additions and 395 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/troubleshooting.mdx
View File

@@ -39,7 +39,7 @@ Add the following to your `compose.yaml` to use Google's DNS:
```yaml
---
services:
jellyseerr:
seerr:
dns:
- 8.8.8.8
```
@@ -47,7 +47,7 @@ or for Cloudflare's DNS:
```yaml
---
services:
jellyseerr:
seerr:
dns:
- 1.1.1.1
```
@@ -55,7 +55,7 @@ or for Quad9's DNS:
```yaml
---
services:
jellyseerr:
seerr:
dns:
- 9.9.9.9
```
@@ -97,19 +97,19 @@ You can try them all and see which one works for your network.
</TabItem>
</Tabs>
### Option 2: Use Jellyseerr through a proxy
### Option 2: Use Seerr through a proxy
If you can't change your DNS servers or force IPV4 resolution, you can use Jellyseerr through a proxy.
If you can't change your DNS servers or force IPV4 resolution, you can use Seerr through a proxy.
In some places (like China), the ISP blocks not only the DNS resolution but also the connection to the TMDB API.
You can configure Jellyseerr to use a proxy with the [HTTP(S) Proxy](/using-jellyseerr/settings/general#enable-proxy-support) setting.
You can configure Seerr to use a proxy with the [HTTP(S) Proxy](/using-seerr/settings/general#enable-proxy-support) setting.
### Option 3: Force IPV4 resolution first
Sometimes there are configuration issues with IPV6 that prevent the hostname resolution from working correctly.
You can try to force the resolution to use IPV4 first by going to `Settings > Networking > Advanced Networking` and enabling `Force IPv4 Resolution First` setting and restarting Jellyseerr.
You can try to force the resolution to use IPV4 first by going to `Settings > Networking > Advanced Networking` and enabling `Force IPv4 Resolution First` setting and restarting Seerr.
### Option 4: Check that your server can reach TMDB API
@@ -119,7 +119,7 @@ Make sure that your server can reach the TMDB API by running the following comma
<TabItem value="docker-cli" label="Docker CLI">
```bash
docker exec -it jellyseerr sh -c "apk update && apk add curl && curl -L https://api.themoviedb.org"
docker exec -it seerr sh -c "apk update && apk add curl && curl -L https://api.themoviedb.org"
```
</TabItem>
@@ -127,7 +127,7 @@ docker exec -it jellyseerr sh -c "apk update && apk add curl && curl -L https://
<TabItem value="docker-compose" label="Docker Compose">
```bash
docker compose exec jellyseerr sh -c "apk update && apk add curl && curl -L https://api.themoviedb.org"
docker compose exec seerr sh -c "apk update && apk add curl && curl -L https://api.themoviedb.org"
```
</TabItem>
@@ -161,16 +161,16 @@ This can happen if you have a new installation of Jellyfin/Emby or if you have c
### Solution: Reset admin access
1. Back up your `settings.json` file (located in your Jellyseerr data directory)
2. Stop the Jellyseerr container/service
1. Back up your `settings.json` file (located in your Seerr data directory)
2. Stop the Seerr container/service
3. Delete the `settings.json` file
4. Start Jellyseerr again
4. Start Seerr again
5. This will force the setup page to appear
6. Go through the setup process with the same login details
7. You can skip the services setup
8. Once you reach the discover page, stop Jellyseerr
8. Once you reach the discover page, stop Seerr
9. Restore your backed-up `settings.json` file
10. Start Jellyseerr again
10. Start Seerr again
This process should restore your admin privileges while preserving your settings.