Jellyseer error

[Sabering1]

Steps to reproduce

1. Install jellyseer via community containers beta
2. try to access it
3. it wont load

Expected behavior

Web app loads

Actual behavior

Nothing loads

Other information

debian latest nextcloud beta 10.50

Output of sudo docker info

Client: Docker Engine - Community
Version: 27.5.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4
Path: /usr/libexec/docker/cli-plugins/docker-compose

Server:
Containers: 25
Running: 22
Paused: 0
Stopped: 3
Images: 46
Server Version: 27.5.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.2.4-0-g6c52b3f
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-28-amd64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.5GiB
Name: saberserver
ID: d7a9c23a-5f3b-4e6a-9597-64eb79be8320
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Docker run command or docker-compose file that you used

sudo docker run --init --sig-proxy=false --name nextcloud-aio-mastercontainer --env AIO_COMMUNITY_CONTAINERS="jellyfin jellyseerr memories fail2ban npmplus" --env NEXTCLOUD_ENABLE_DRI_DEVICE=true --restart always --publish 80:80 --publish 8080:8080 --publish 8443:8443 --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config --volume /var/run/docker.sock:/var/run/docker.sock:ro nextcloud/all-in-one:beta

Other valuable info

2025-02-01T19:20:29.064598023Z [WARN tini (7)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2025-02-01T19:20:29.064629579Z Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2025-02-01T19:20:29.064635117Z To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2025-02-01T19:20:29.736563995Z
2025-02-01T19:20:29.736593880Z > [email protected] start /app
2025-02-01T19:20:29.736598831Z > NODE_ENV=production node dist/index.js
2025-02-01T19:20:29.736602730Z
2025-02-01T19:20:31.650680040Z 2025-02-01T19:20:31.649Z [�[32minfo�[39m]: Commit Tag: $GIT_SHA
2025-02-01T19:20:32.367516719Z 2025-02-01T19:20:32.366Z [�[32minfo�[39m]: Starting Overseerr version 2.3.0
2025-02-01T19:20:32.685639935Z (node:19) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
2025-02-01T19:20:32.685659723Z (Use node --trace-deprecation ... to show where the warning was created)
2025-02-01T19:20:33.139496570Z 2025-02-01T19:20:33.139Z [�[34mdebug�[39m][Settings Migrator]: Checking migration '0001_migrate_hostname.js'...
2025-02-01T19:20:33.141384453Z 2025-02-01T19:20:33.141Z [�[34mdebug�[39m][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'...
2025-02-01T19:20:33.143351339Z 2025-02-01T19:20:33.143Z [�[34mdebug�[39m][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'...
2025-02-01T19:20:33.144498744Z 2025-02-01T19:20:33.144Z [�[34mdebug�[39m][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'...
2025-02-01T19:20:33.147073003Z 2025-02-01T19:20:33.146Z [�[32minfo�[39m][Notifications]: Registered notification agents
2025-02-01T19:20:33.151637409Z 2025-02-01T19:20:33.151Z [�[32minfo�[39m][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2025-02-01T19:20:33.322374066Z 2025-02-01T19:20:33.322Z [�[32minfo�[39m][Server]: Server ready on port 5055

[szaimen]

Hi, can you post a screenshot of what ypu are currently seeing in the AIO interface here?

[Sabering1]

[szaimen]

Hm... So opening http://ip.address.of.server:5055 did not work?

[Sabering1]

nope

[szaimen]

@Anvil5465 can you please help here? Does it work for you?

[Sabering1]

No api key has been generated in my jellyfin instance too, and i believe you need to generate it for jellyseer to function correctly, but i don't know if its because jellyseer didn't start or what

[Anvil5465]

@Anvil5465 can you please help here? Does it work for you?

I haven't gotten around to testing yet, but I'll give it a go soon!