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
SuggestArr reads your Jellyfin/Plex/Emby watch history, finds similar titles via TMDB, and files requests in Jellyseerr or Overseerr automatically. Requested in discussion #2449.
Stack: Vue client + Python (uvicorn/ASGI) backend. npm ci && npm run build in client/, deps via uv pip install -r api_service/requirements.txt.
Layout taken from docker/Dockerfile: the built client is copied to /opt/suggestarr/static/, and swagger-ui-dist from the client's node_modules to static/swagger-ui — the backend serves both from there, so skipping that step leaves a blank page.
Start command from config/supervisord.conf:uvicorn api_service.app:asgi_app --host 0.0.0.0 --port 5000. Upstream runs it under supervisord; here it is a plain systemd unit.
CONFIG_DIR=/opt/suggestarr_data keeps configuration and the local database outside the app directory so CLEAN_INSTALL updates do not wipe them.
Note: it files requests on its own. Flagged as a warning to keep approval enabled in Jellyseerr/Overseerr and start with a conservative job config — otherwise it fills disks quickly.
Everything is configured through the setup wizard at http://:5000: your media server (Jellyfin/Plex/Emby), a TMDB API key, and the Jellyseerr or Overseerr instance that receives the requests.
SuggestArr files requests automatically. Start with a conservative job configuration and keep approval enabled in Jellyseerr/Overseerr, otherwise it can fill your disks faster than expected.
Configuration and the local database live in /opt/suggestarr_data, outside the app directory, so they survive updates.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
The below is 100 % written by AI. I asked Al to help me set it up and review the setup.
Testing feedback for the SuggestArr LXC script:
Overall, the install is working very well. Setup completed successfully and Plex, TMDb and Seerr all connected correctly. Plex users were detected, recommendation Preview works, and with Approve First enabled the recommendations stay in SuggestArr and nothing is automatically sent to Seerr.
A few things I noticed during testing:
CONFIG_DIR=/opt/suggestarr_data is correctly set in /opt/suggestarr.env, but /opt/suggestarr_data remains empty.
The live files are instead being written to: /opt/suggestarr/config/config_files/
including requests.db, config.yaml, secret.key and app.log.
This may mean the advertised update-safe persistence through /opt/suggestarr_data is currently not working.
During installation I selected No for provisioning root SSH keys and No for root SSH access, but ssh.service and ssh.socket were still enabled and port 22 was listening. I disabled both manually.
requests.db, config.yaml and app.log were initially mode 644. I changed the sensitive files to 600 and the config directories to 700.
I checked the actual configured secret values against both app.log and the systemd journal and found 0 secret values exposed.
The SuggestArr service itself is healthy and responding normally on port 5000, and the LXC is unprivileged with no extra storage mounts.
I’ll keep running it for the next week and report back on scheduled jobs, reboots, updates and general stability. So far the actual SuggestArr experience has been excellent.
Activity
github-actions commentedon Aug 4, 2026
The SuggestArr script is ready for testing:
Everything is configured through the setup wizard at http://:5000: your media server (Jellyfin/Plex/Emby), a TMDB API key, and the Jellyseerr or Overseerr instance that receives the requests.
SuggestArr files requests automatically. Start with a conservative job configuration and keep approval enabled in Jellyseerr/Overseerr, otherwise it can fill your disks faster than expected.
Configuration and the local database live in /opt/suggestarr_data, outside the app directory, so they survive updates.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1534106591962333194
schinguhl commentedon Aug 5, 2026
The script worked as intended. No errors. SuggestArr works just fine.
hiSweid commentedon Aug 10, 2026
Worked for me without a problem for two days, thank you!
Dutchsnof commentedon Aug 12, 2026
Worked for me aswel!
github-actions commentedon Aug 12, 2026
A PR has been created for suggestarr: community-scripts/ProxmoxVE#16449
MatDaBoss commentedon Aug 12, 2026
The below is 100 % written by AI. I asked Al to help me set it up and review the setup.
Testing feedback for the SuggestArr LXC script:
Overall, the install is working very well. Setup completed successfully and Plex, TMDb and Seerr all connected correctly. Plex users were detected, recommendation Preview works, and with Approve First enabled the recommendations stay in SuggestArr and nothing is automatically sent to Seerr.
A few things I noticed during testing:
CONFIG_DIR=/opt/suggestarr_datais correctly set in/opt/suggestarr.env, but/opt/suggestarr_dataremains empty./opt/suggestarr/config/config_files/including
requests.db,config.yaml,secret.keyandapp.log./opt/suggestarr_datais currently not working.ssh.serviceandssh.socketwere still enabled and port 22 was listening. I disabled both manually.requests.db,config.yamlandapp.logwere initially mode644. I changed the sensitive files to600and the config directories to700.app.logand the systemd journal and found 0 secret values exposed.The SuggestArr service itself is healthy and responding normally on port 5000, and the LXC is unprivileged with no extra storage mounts.
I’ll keep running it for the next week and report back on scheduled jobs, reboots, updates and general stability. So far the actual SuggestArr experience has been excellent.
michelroegl-brunner commentedon Aug 13, 2026
Merged with #16449 in ProxmoxVE
github-actions commentedon Aug 13, 2026
Files deleted with PR #2176