Skip to content

Web UI down - Error 500 #1381

@alexhochreiter

Description

@alexhochreiter

I noticed today that I cannot open the webui anymore.
I am greeted with this error message:

500 - Internal Server Error

Your request caused an internal server error. This has been logged and our developers will implement a fix shortly.

The docker logs do not show anything related when I open the webui, but some access like log lines.
The docker container worked without any problems for

tubesync    |   No migrations to apply.
tubesync    | s6-rc: info: service tubesync-init successfully started
tubesync    | s6-rc: info: service gunicorn: starting
tubesync    | s6-rc: info: service gunicorn successfully started
tubesync    | s6-rc: info: service nginx: starting
tubesync    | s6-rc: info: service huey-network: starting
tubesync    | s6-rc: info: service huey-net-limited: starting
tubesync    | s6-rc: info: service huey-filesystem: starting
tubesync    | s6-rc: info: service huey-database: starting
tubesync    | s6-rc: info: service huey-net-limited successfully started
tubesync    | s6-rc: info: service huey-network successfully started
tubesync    | s6-rc: info: service nginx successfully started
tubesync    | s6-rc: info: service huey-filesystem successfully started
tubesync    | s6-rc: info: service huey-database successfully started
tubesync    | s6-rc: info: service legacy-services: starting
tubesync    | s6-rc: info: service legacy-services successfully started
tubesync    | [2026-02-04 16:43:14 +0100] [149] [INFO] Starting gunicorn 23.0.0
tubesync    | [2026-02-04 16:43:14 +0100] [149] [INFO] Listening at: http://127.0.0.1:8080 (149)
tubesync    | [2026-02-04 16:43:14 +0100] [149] [INFO] Using worker: sync
tubesync    | [2026-02-04 16:43:14 +0100] [194] [INFO] Booting worker with pid: 194
tubesync    | [2026-02-04 16:43:14 +0100] [195] [INFO] Booting worker with pid: 195
tubesync    | [2026-02-04 16:43:14 +0100] [196] [INFO] Booting worker with pid: 196
tubesync    | 2026-02-04 16:43:30,656 [tubesync/INFO] waiting for errors: 429 (00:00:00): aKZ1d7U8OLI
tubesync    | 2026-02-04 16:43:30,721 [tubesync/INFO] Downloading media: aKZ1d7U8OLI (UUID: 19314aa2-72bf-4b28-8f30-1eeb020e6977) to: "/downloads/video/bla/2018-03-11_blabla_1080p-avc1-opus.mkv"
tubesync    | 192.168.0.100 - alex [04/Feb/2026:16:43:37 +0100] "GET / HTTP/1.1" 500 268 "-" "Mozilla/5.0 ........"
tubesync    | 127.0.0.1 - - [04/Feb/2026:16:43:45 +0100] "GET /ping HTTP/1.1" 502 556 "-" "Mozilla/5.0 ........."
tubesync    | 2026/02/04 16:43:45 [error] 189#189: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /ping HTTP/1.1", upstream: "http://127.0.0.1:4406/ping", host: "127.0.0.1:4416"
tubesync    | WARNING: [youtube] [pot:bgutil:http] HTTP Error reaching GET /ping (caused by <HTTPError 502: Bad Gateway>)
tubesync    | WARNING: [youtube] aKZ1d7U8OLI: Some web client https formats have been skipped as they are missing a url. YouTube is forcing SABR streaming for this client. See  https://github.com/yt-dlp/yt-dlp/issues/12482  for more details

Is there any way I can debug or fix this?

Here is the docker-compose file in case it is useful:

services:
  tubesync:
    image: ghcr.io/meeb/tubesync:latest
    container_name: tubesync
    restart: unless-stopped
    stop_grace_period: 30m
    ports:
      - 4848:4848
    volumes:
      - /var/tubesync/config:/config:z
      - /var/nas_nfs/media/youtube/tubesync-downloads:/downloads:z
    environment:
      - TZ=Europe/Vienna
      - PUID=1000
      - PGID=1000
      - HTTP_USER=.......
      - HTTP_PASS=........

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions