Hello. I just moved from Overseerr to Seerr 3.0.1. That seemed to go prety smoothly, but I wanted to also move from SQLite. I reconfigured my instance to use postgres and started it to build the tables. I then shut it down and used pgloader in docker as described in the guide. I received some errors. After restart Seer all my requests were missing. Attached is the output from pgloader. Thanks!
#Errors Migrating to Postgres
17 messages · Page 1 of 1 (latest)
It shows that everything except migrations table and discover slide worked
After restarting are you sure youre connected to postgres?
Show me your compose
Its very likely that youre not properly connected and it just remade an sqlite db
OK, here is my compose:
seerr:
<<: *default-proxy-data
image: ghcr.io/seerr-team/seerr:latest
init: true
container_name: seerr
# depends_on:
# # - plex
# - sonarr
# - radarr
networks:
traefik_proxy:
ipv4_address: "192.168.1.201"
default:
# ports:
# - "5055:3000"
environment:
- TZ=${TZ}
- DB_TYPE=postgres # Which DB engine to use, either sqlite or postgres. The default is sqlite.
- DB_HOST=${SEERR_DB_HOST} # (optional) The host (URL) of the database. The default is "localhost".
# - DB_PORT="5432" # (optional) The port to connect to. The default is "5432".
- DB_USER=${SEERR_DB_USER} # (required) Username used to connect to the database.
- DB_PASS=${SEERR_DB_PASS} # (required) Password of the user used to connect to the database.
# - DB_NAME="seerr" # (optional) The name of the database to connect to. The default is "seerr".
user: ${PUID}:${PGID}
volumes:
- ${USERDIR_ISCSI}/docker/seerr/config:/app/config
healthcheck:
test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1
start_period: 20s
timeout: 3s
interval: 15s
retries: 3
And the logs too
I rolled back so I just need a few minuteds to step through it again and generate new logs
May need to turn up the logging...
2026-02-14T20:40:07.789Z [info]: Commit Tag: 789bcc8eec3414da373328e374c2edb1abc3ac0d
2026-02-14T20:40:08.347Z [info]: Starting Seerr version 3.0.1
2026-02-14T20:40:09.017Z [debug][Settings Migrator]: Checking migration '0001_migrate_hostname.js'...
2026-02-14T20:40:09.019Z [debug][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'...
2026-02-14T20:40:09.020Z [debug][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'...
2026-02-14T20:40:09.022Z [debug][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'...
2026-02-14T20:40:09.022Z [debug][Settings Migrator]: Checking migration '0005_migrate_network_settings.js'...
2026-02-14T20:40:09.023Z [debug][Settings Migrator]: Checking migration '0006_remove_lunasea.js'...
2026-02-14T20:40:09.024Z [debug][Settings Migrator]: Checking migration '0007_migrate_arr_tags.js'...
2026-02-14T20:40:09.026Z [debug][Settings Migrator]: Checking migration '0008_migrate_blacklist_to_blocklist.js'...
2026-02-14T20:40:09.029Z [info][Notifications]: Registered notification agents
2026-02-14T20:40:09.091Z [info][Jobs]: Scheduled jobs loaded
2026-02-14T20:40:09.242Z [info][Server]: Server ready on port 5055
2026-02-14T20:41:00.020Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-02-14T20:42:00.015Z [debug][Jobs]: Starting scheduled job: Download Sync
2026-02-14T20:43:00.016Z [debug][Jobs]: Starting scheduled job: Download Sync
Looks like my settings are there but Requests and Users are empty
user table only has 1 row - my account. media_request has data in it.
Then yiu might need to rerun the pgloader. Pgloader is a hit or miss. Even i had to do 5 reruns to get it properly to work 😅
Rerun again with a fresh postgres db
Haha. will do
So I ran it a few more times and the users table eventually showed up! I then manually kicked off my *arr scans , Plex Full Library Scan, and Media Availability Scan. Requests populated and I think things are looking pretty good. Thank you!