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
Copy file name to clipboardExpand all lines: docs/getting-started/docker.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ docker run -d \
37
37
-p 5055:5055 \
38
38
-v /path/to/appdata/config:/app/config \
39
39
--restart unless-stopped \
40
-
ghcr.io/fallenbagel/jellyseerr
40
+
fallenbagel/jellyseerr
41
41
```
42
42
43
43
To run the container as a specific user/group, you may optionally add `--user=[ user | user:group | uid | uid:gid | user:gid | uid:group ]` to the above command.
Copy file name to clipboardExpand all lines: docs/troubleshooting.mdx
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,12 @@ In some places (like China), the ISP blocks not only the DNS resolution but also
105
105
106
106
You can configure Jellyseerr to use a proxy with the [HTTP(S) Proxy](/using-jellyseerr/settings/general#https-proxy) setting.
107
107
108
+
### Option 3: Force IPV4 resolution first
109
+
110
+
Sometimes there are configuration issues with IPV6 that prevent the hostname resolution from working correctly.
111
+
112
+
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.
113
+
108
114
### Option 4: Check that your server can reach TMDB API
109
115
110
116
Make sure that your server can reach the TMDB API by running the following command:
@@ -146,3 +152,26 @@ In a PowerShell window:
146
152
147
153
If you can't get a response, then your server can't reach the TMDB API.
148
154
This is usually due to a network configuration issue or a firewall blocking the connection.
155
+
156
+
## Account does not have admin privileges
157
+
158
+
If your admin account no longer has admin privileges, this is typically because your Jellyfin/Emby user ID has changed on the server side.
159
+
160
+
This can happen if you have a new installation of Jellyfin/Emby or if you have changed the user ID of your admin account.
161
+
162
+
### Solution: Reset admin access
163
+
164
+
1. Back up your `settings.json` file (located in your Jellyseerr data directory)
165
+
2. Stop the Jellyseerr container/service
166
+
3. Delete the `settings.json` file
167
+
4. Start Jellyseerr again
168
+
5. This will force the setup page to appear
169
+
6. Go through the setup process with the same login details
170
+
7. You can skip the services setup
171
+
8. Once you reach the discover page, stop Jellyseerr
172
+
9. Restore your backed-up `settings.json` file
173
+
10. Start Jellyseerr again
174
+
175
+
This process should restore your admin privileges while preserving your settings.
176
+
177
+
If you still encounter issues, please reach out on our support channels.
0 commit comments