You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update Unraid install and migration guides with dual permission methods (#2532)
Co-authored-by: Mindaugas Jonkus <mjonkusgmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Ludovic Ortega <github@mail.adminafk.fr>
@@ -4,6 +4,9 @@ description: Install Seerr using Unraid
4
4
sidebar_position: 3
5
5
---
6
6
7
+
importTabsfrom'@theme/Tabs';
8
+
importTabItemfrom'@theme/TabItem';
9
+
7
10
# Unraid
8
11
9
12
:::warning
@@ -14,76 +17,160 @@ Third-party installation methods are maintained by the community. The Seerr team
14
17
This method is not recommended for most users. It is intended for advanced users who are using Unraid.
15
18
:::
16
19
20
+
## Template installation
17
21
18
-
If an official Unraid Community Applications template for Seerr isn't available in your catalog, you can install Seerr manually using Unraid's Docker UI.
22
+
Several templates from Unraid Community are available right now
23
+
-[Unraid Community Apps](https://unraid.net/community/apps#community-apps-iframe)
19
24
20
-
## Fresh Installation
25
+
In case you still want to do it manually, please follow the instructions below.
21
26
22
-
### 1. Create the config directory
27
+
##Manual Installation
23
28
24
-
:::note
25
-
Seerr is now rootless. Unraid typically runs Docker containers as `nobody:users` (UID 99, GID 100), but Seerr now runs internally as UID 1000, GID 1000. This creates a permission mismatch.
26
-
:::
29
+
Before proceeding, choose which installation method best suits your server:
27
30
28
-
:::info
29
-
**If migrating**: Copy your existing Jellyseerr/Overseerr config files (e.g., from `/mnt/user/appdata/overseerr/` or `/mnt/user/appdata/jellyseerr`) to `/mnt/user/appdata/seerr`, then apply the permissions below
30
-
:::
31
+
**Seerr Default** (`UID 1000:1000`) — Runs with the container's native `node` user. Matches the official image, but may break SMB share access, trigger "Fix Common Problems" warnings, and cause issues with backup plugins (such as CA Appdata Backup) and network integrations (such as Tailscale).
31
32
32
-
Open the Unraid terminal and run:
33
+
**Unraid Default** (`UID 99:100`) — Runs with Unraid's native `nobody:users` ownership. Follows Unraid best practices, but overrides Seerr's built-in rootless user and may cause compatibility issues with future Seerr updates.
Then click **Add another Path, Port, Variable** to add:
46
+
### 2. Set folder permissions
55
47
56
-
**Port:**
57
-
| Field | Value |
58
-
|---|---|
59
-
| Container Port |`5055`|
60
-
| Host Port |`5055`|
61
-
| Connection Type |`TCP`|
48
+
```bash
49
+
chown -R 1000:1000 /mnt/user/appdata/seerr
50
+
```
62
51
63
-
**Path:**
64
-
| Field | Value |
65
-
|---|---|
66
-
| Container Path |`/app/config`|
67
-
| Host Path |`/mnt/user/appdata/seerr`|
52
+
### 3. Add the Docker container
68
53
69
-
**Variable:**
70
-
| Field | Value |
71
-
|---|---|
72
-
| Key |`TZ`|
73
-
| Value | Your [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (e.g., `America/New_York`) |
54
+
:::warning
55
+
The **Extra Parameters** field is critical. You **must** add `--init --restart=unless-stopped` (see table below). Without `--init`, the container will not handle signals properly or shut down cleanly. Without `--restart=unless-stopped`, the container will not automatically restart after a reboot.
74
56
75
-
**Variable (optional):**
76
-
| Field | Value |
77
-
|---|---|
78
-
| Key |`LOG_LEVEL`|
79
-
| Value |`info`|
57
+
To see the **Extra Parameters** field, click **Basic View** in the top-right corner of the template page to switch to the advanced editor.
58
+
:::
80
59
81
-
Click **Apply**to create and start the container.
60
+
Navigate to the **Docker**tab in Unraid and click **Add Container**. Fill in the following:
Open the WebUI at `http://<your-unraid-ip>:5055` and follow the setup wizard.
72
+
Then click **Add another Path, Port, Variable** to add:
86
73
87
-
:::info
88
-
The `--init` flag in **Extra Parameters** is required. Seerr does not include its own init process, so `--init` ensures proper signal handling and clean container shutdowns.
89
-
:::
74
+
**Port:**
75
+
| Field | Value |
76
+
|---|---|
77
+
| Container Port |`5055`|
78
+
| Host Port |`5055`|
79
+
| Connection Type |`TCP`|
80
+
81
+
**Path:**
82
+
| Field | Value |
83
+
|---|---|
84
+
| Container Path |`/app/config`|
85
+
| Host Path |`/mnt/user/appdata/seerr`|
86
+
87
+
**Variable:**
88
+
| Field | Value |
89
+
|---|---|
90
+
| Key |`TZ`|
91
+
| Value | Your [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (e.g., `America/New_York`) |
92
+
93
+
**Variable (optional):**
94
+
| Field | Value |
95
+
|---|---|
96
+
| Key |`LOG_LEVEL`|
97
+
| Value |`info`|
98
+
99
+
Click **Apply** to create and start the container.
100
+
101
+
### 4. Access Seerr
102
+
103
+
Open the WebUI at `http://<your-unraid-ip>:5055` and follow the setup wizard.
The **Extra Parameters** field is critical. You **must** add `--init --restart=unless-stopped --user 99:100` (see table below). Without `--init`, the container will not handle signals properly or shut down cleanly. Without `--restart=unless-stopped`, the container will not automatically restart after a reboot. The `--user 99:100` parameter runs the container process with Unraid's default UID/GID and avoids permission errors accessing your shares without changing host folder ownership.
126
+
127
+
To see the **Extra Parameters** field, click **Basic View** in the top-right corner of the template page to switch to the advanced editor.
128
+
:::
129
+
130
+
Navigate to the **Docker** tab in Unraid and click **Add Container**. Fill in the following:
Copy file name to clipboardExpand all lines: docs/migration-guide.mdx
+16-56Lines changed: 16 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -258,63 +258,23 @@ Refer to [Seerr Unraid Documentation](/getting-started/third-parties/unraid), al
258
258
259
259
Seerr will automatically migrate your existing Overseerr or Jellyseerr data on first startup. No manual database migration is needed.
260
260
261
-
1. Stop and remove the old Overseerr (or Jellyseerr) container from the Unraid **Docker** tab. Click the container icon, then **Stop**, then **Remove**. **⚠️ Do not delete the appdata folder ⚠️**
261
+
**1. Stop the existing container**
262
+
In the Unraid **Docker** tab, stop your Overseerr (or Jellyseerr) container.
263
+
**⚠️ Do not remove the container or delete the appdata folder yet ⚠️**
262
264
263
-
2. Back up your existing appdata folder:
265
+
**2. Copy existing data to Seerr appdata**
266
+
Open the Unraid terminal and copy your existing appdata folder into the new Seerr appdata directory:
264
267
```bash
265
-
cp -a /mnt/user/appdata/overseerr /mnt/user/appdata/overseerr-backup
268
+
cp -a /mnt/user/appdata/overseerr /mnt/user/appdata/seerr
266
269
```
267
270
268
-
3. Fix config folder permissions — Seerr runs as the `node` user (UID 1000) instead of root:
269
-
```bash
270
-
chown -R 1000:1000 /mnt/user/appdata/overseerr
271
-
```
272
-
For Jellyseerr users, replace `overseerr` with `jellyseerr` in the path above.
273
-
274
-
4. Add a new container in the Unraid **Docker** tab. Click **Add Container** and fill in the following:
Then click **Add another Path, Port, Variable** to add:
288
-
289
-
**Port:**
290
-
| Field | Value |
291
-
|---|---|
292
-
| Container Port |`5055`|
293
-
| Host Port |`5055`|
294
-
| Connection Type |`TCP`|
295
-
296
-
**Path** — point this to your existing config folder:
297
-
| Field | Value |
298
-
|---|---|
299
-
| Container Path |`/app/config`|
300
-
| Host Path |`/mnt/user/appdata/overseerr`|
301
-
302
-
For Jellyseerr users, use `/mnt/user/appdata/jellyseerr`.
303
-
304
-
**Variable:**
305
-
| Field | Value |
306
-
|---|---|
307
-
| Key |`TZ`|
308
-
| Value | Your [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (e.g., `America/New_York`) |
309
-
310
-
**Variable (optional):**
311
-
| Field | Value |
312
-
|---|---|
313
-
| Key |`LOG_LEVEL`|
314
-
| Value |`info`|
315
-
316
-
5. Click **Apply** to start the container. Check the container logs to confirm the automatic migration completed successfully.
317
-
318
-
:::tip
319
-
If you are using a reverse proxy (such as SWAG or Nginx Proxy Manager), update your proxy configuration to point to the new container name `seerr`. The default port remains `5055`.
320
-
:::
271
+
*(For Jellyseerr users, replace `overseerr` with `jellyseerr` in the paths).*
272
+
273
+
**3. Set permissions and install Seerr**
274
+
Follow the [Unraid Installation Guide](/getting-started/third-parties/unraid#2-set-folder-permissions), **starting from step 2** — this covers setting the correct folder permissions and adding the Docker container. The guide offers two permission methods (**Seerr Default** and **Unraid Default**), each with trade-offs — read the descriptions before choosing.
275
+
276
+
**4. Start the new Seerr app**
277
+
Start the newly created Seerr container. Check the container logs to confirm the automatic migration completed successfully.
278
+
279
+
**5. Remove the old app**
280
+
Once you have confirmed Seerr is working properly and your data has successfully migrated, you can safely **Remove** the old Overseerr (or Jellyseerr) container from Unraid.
0 commit comments