[GH-ISSUE #55] [Bug Report] Docker Not Detecting credentials.json #43

New issue

Closed

opened 2026-02-27 04:57:15 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 04:57:15 +03:00

Owner

Originally created by @treysu on GitHub (Aug 19, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/55

Originally assigned to: @Googolplexed0 on GitHub.

Bug Description
When running the docker image and supplying the credentials.json file generated on another machine, Zotify still asks for login.

Bug Triggering Command
I run my docker containers on a headless Linux VM, so I am unable to click the login link. Instead, I am generating my credentials file on Windows and trying to pass the pre-generated token to Zotify by supplying my credentials.json file to the container.

I have tried mapping a docker volume pointed to /root/.config/zotify (which does properly create the config in the location next to credentials.json). I have also tried using the CREDENTIALS_LOCATION environment variable to no visible success.

The command that caused the error/crash, including relevant url arguments.

Additional Context
I have also tried creating an SSH tunnel from my Windows desktop to the VM running the container, tunneling port 4381 and exposing it in the docker run command. This would ideally let me click the link directly from the browser in Windows, but I was also not able to get this working.

Originally created by @treysu on GitHub (Aug 19, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/55 Originally assigned to: @Googolplexed0 on GitHub. **Bug Description** When running the docker image and supplying the credentials.json file generated on another machine, Zotify still asks for login. **Bug Triggering Command** I run my docker containers on a headless Linux VM, so I am unable to click the login link. Instead, I am generating my credentials file on Windows and trying to pass the pre-generated token to Zotify by supplying my `credentials.json` file to the container. I have tried mapping a docker volume pointed to `/root/.config/zotify` (which does properly create the config in the location next to `credentials.json`). I have also tried using the `CREDENTIALS_LOCATION` environment variable to no visible success. The command that caused the error/crash, including relevant url arguments. **Additional Context** I have also tried creating an SSH tunnel from my Windows desktop to the VM running the container, tunneling port 4381 and exposing it in the docker run command. This would ideally let me click the link directly from the browser in Windows, but I was also not able to get this working.

kerem

2026-02-27 04:57:15 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 04:57:15 +03:00

Author

Owner

@treysu commented on GitHub (Aug 19, 2025):

Figured out the root of the issue. The problem was that config.json is saved inside /root/.config/zotify, but credentials.json is saved inside /root/.local/share/zotify.

@treysu commented on GitHub (Aug 19, 2025): Figured out the root of the issue. The problem was that `config.json` is saved inside `/root/.config/zotify`, but `credentials.json` is saved inside `/root/.local/share/zotify`.