My zurg-testing:latest (v0.9.3-final) container gets bad_token (401) from the Real-Debrid API. The same token works when I call the API directly from the same host.
Verification (from the same machine that runs Zurg):
curl -X GET "https://api.real-debrid.com/rest/1.0/user" -H "Authorization: Bearer MY_TOKEN"
Returns 200 and correct user JSON.
Config (config.yml):
Error in Zurg logs:
ERROR realdebrid Error when executing the get torrents request: api response error: bad_token (status code: 401) (code: 8)
Also see the same for the user info request on startup.
Setup:
- Image:
ghcr.io/debridmediamanager/zurg-testing:latest
- Volumes:
./config.yml:/zurg/config.yml, ./zurgdata:/zurg/data
- Tried: fresh run, cleared
zurgdata, re-pulled image — issue persists.
- Config is read (logs show "Loading config file ./config.yml", "Config version: v1").
So the token is valid and works with Authorization: Bearer from this host; Zurg still gets 401. Is the token sent to Real-Debrid exactly as Authorization: Bearer <token>, or could there be a known issue with token handling in v0.9.3?
docker-compose (Zurg + rclone + Jellyfin):
services:
zurg:
image: ghcr.io/debridmediamanager/zurg-testing:latest
container_name: zurg
restart: unless-stopped
ports:
- "9999:9999"
volumes:
- ./zurgdata:/zurg/data
- ./config.yml:/zurg/config.yml
rclone:
image: rclone/rclone:latest
container_name: rclone
restart: unless-stopped
depends_on:
- zurg
devices:
- /dev/fuse:/dev/fuse
cap_add:
- SYS_ADMIN
security_opt:
- apparmor:unconfined
volumes:
- /mnt/zurg:/data:shared
- ./rclone.conf:/config/rclone/rclone.conf
command: "mount zurg: /data --allow-other --vfs-cache-mode full"
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
restart: unless-stopped
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- ./jellyfin-config:/config
- /mnt/zurg:/data/debrid
ports:
- "8096:8096"
depends_on:
- rclone
My zurg-testing:latest (v0.9.3-final) container gets bad_token (401) from the Real-Debrid API. The same token works when I call the API directly from the same host.
Verification (from the same machine that runs Zurg):
curl -X GET "https://api.real-debrid.com/rest/1.0/user" -H "Authorization: Bearer MY_TOKEN"Returns 200 and correct user JSON.
Config (config.yml):
Error in Zurg logs:
ERROR realdebrid Error when executing the get torrents request: api response error: bad_token (status code: 401) (code: 8)Also see the same for the user info request on startup.
Setup:
ghcr.io/debridmediamanager/zurg-testing:latest./config.yml:/zurg/config.yml, ./zurgdata:/zurg/datazurgdata, re-pulled image — issue persists.So the token is valid and works with
Authorization: Bearerfrom this host; Zurg still gets 401. Is the token sent to Real-Debrid exactly asAuthorization: Bearer <token>, or could there be a known issue with token handling in v0.9.3?docker-compose (Zurg + rclone + Jellyfin):