[Bug]: Authorization Error

[juanbeniteza]

Checklist

• I searched existing issues first.
• I removed secrets, tokens, passwords, and private URLs from logs and screenshots.

What broke?
A clear and concise description of the bug.

Which part of Sake is affected?

• Web app
• API
• KOReader plugin
• Sync/progress/device flow
• Search/download providers
• Self-hosting / deployment
• Something else

Steps to reproduce

1. Go to '...'
2. Click / run / sync '...'
3. Observe '...'

What did you expect to happen?
A clear and concise description of the expected behavior.

What happened instead?
Describe the actual behavior, error message, or broken state.

Environment

• Sake version / image tag / commit: [e.g. 2026.03.28.1, latest, or a commit SHA]
• Setup: [e.g. Docker prebuilt image, Docker from source, local Bun dev]
• Database: [e.g. libSQL/Turso, local file-backed libSQL]
• Storage: [e.g. Cloudflare R2, MinIO, SeaweedFS, other S3-compatible storage]
• Enabled search providers: [e.g. none, openlib,gutenberg, zlib]
• Browser + OS: [if relevant]
• KOReader device + KOReader version: [if relevant]

Logs, screenshots, or traces
Add any useful logs, screenshots, console errors, or API responses here.

Additional context
Anything else that might help reproduce or narrow this down.

after i login successfully all the request get a 401 error

[Jalsemgeest]

+1 - getting 401s for the newly created user after a clean .selfhost.yaml docker-compose turn up.

[Sudashiii]

Hmm okay, I tried it a few days ago and could not really replicate. I've changed something about auth recently, maybe thats the culprit. Have you tried older versions?

[Sudashiii]

Can i get a bit more information?

Is it hosted an a remote device? Are you accessing through a URL or IP directly? Have you used a upgraded and did the version from before work? Are there any logs? Http or Https? etc..

[Jalsemgeest]

Not to takeover juanbeniteza's issue, but I'll respond as well in case it's helpful.

I looked into your recent commits and couldn't find anything that looked obvious, but I'm not overly familiar with your the codebase.

I have this hosted on my local home server. I've tried accessing it through IP or a tailscale tunnel. HTTP calls.

For logs, I couldn't find anything particularly interesting from the docker containers, just like:

[2026-04-17 18:54:00.745 +0000] WARN (sake): Authentication required
    service: "sake"
    env: "production"
    requestId: "69bcf565-bcc5-460e-80c0-8c5b13071735"
    method: "GET"
    route: "/api/library/shelves"
    event: "auth.denied"
    pathname: "/api/library/shelves"

I will say that I do see some JS errors on web, like this:

Uncaught (in promise) TypeError: crypto.randomUUID is not a function
    at h.add (hzWhbp_A.js:1:189)
    at js.loadShelves (4.DSKg1JQG.js:1:81937)
    at async Zs.initialize (4.DSKg1JQG.js:1:94745)

Particularly when I navigate to /library. Otherwise, all network calls just 401 for /list, /api/auth/api-keys, /api/devices, or /api/auth/me to name a few.

[Sudashiii]

Would you two mind to try out #71 before i merge?

@Jalsemgeest @juanbeniteza

[Jalsemgeest]

Unfortuantely this doesn't seem to be working for me still with the change.

I'm still seeing auth.denied errors in the logs for sake-selfhost.

Things I tried:

1. I just tried this out by checking out the change first on the existing repo and it didn't work - rebuilding containers from scratch.
2. I then deleted my containers and the clones folder. I then cloned from scratch at your linked branch. I am still seeing the same issues.

How I start the project:

• docker compose -f docker-examples/docker-compose.prebuilt.selfhost.yaml up -d

This is the logs for sake-seaweedfs:

I0419 14:12:55.304961 raft_common.go:42 TopologyId generated: 72546858-f187-4543-bf04-2f1f85aaf67e
I0419 14:12:55.500128 volume_grpc_client_to_master.go:53 Volume server start with seed master nodes: [seaweedfs:9333]
I0419 14:12:55.500511 volume.go:450 Start Seaweed volume server 30GB 4.17 4a5243886 at 0.0.0.0:8080
I0419 14:12:55.502177 volume_grpc_client_to_master.go:130 Heartbeat to: seaweedfs:9333
I0419 14:12:55.503532 node.go:427 topo adds child DefaultDataCenter
I0419 14:12:55.503600 node.go:427 topo:DefaultDataCenter adds child DefaultRack
I0419 14:12:55.503621 node.go:427 topo:DefaultDataCenter:DefaultRack adds child seaweedfs:8080
I0419 14:12:55.503644 node.go:427 topo:DefaultDataCenter:DefaultRack:seaweedfs:8080 adds child 
I0419 14:12:55.503661 master_grpc_server.go:142 added volume server 0: seaweedfs:8080 (id=seaweedfs:8080, ip=seaweedfs:8080) [e1dda226-aea8-4129-b523-a3136ebbc641]
I0419 14:12:55.503720 master_grpc_server.go:52 found new uuid:seaweedfs:8080 [e1dda226-aea8-4129-b523-a3136ebbc641] , map[seaweedfs:8080:[e1dda226-aea8-4129-b523-a3136ebbc641]]
I0419 14:12:56.060414 masterclient.go:454 .master masterClient reconnection attempt #1
I0419 14:12:56.062691 masterclient.go:216 .master masterClient gRPC stream established to seaweedfs:9333 in 2.223727ms
I0419 14:12:56.063084 master_grpc_server.go:406 + client .master@seaweedfs:9333.19333
I0419 14:12:56.063511 masterclient.go:291 + master@seaweedfs:9333 noticed .master seaweedfs:9333.19333
I0419 14:12:56.504211 filer.go:167 create filer.store.id to 603847274
I0419 14:12:56.504234 configuration.go:29 configured filer store to leveldb2
I0419 14:12:56.504341 filer_server_tus_session.go:400 TUS session cleanup started with interval 1h0m0s
I0419 14:12:56.504811 master_client.go:24 the cluster has 1 filer
I0419 14:12:56.504828 filer_server.go:241 seaweedfs:8888 bootstrap from peers [node_type:"filer"  address:"seaweedfs:8888.18888"  is_add:true  created_at_ns:1776607975189419760]
I0419 14:12:56.504863 filer.go:122 seaweedfs:8888 aggregate from peers [seaweedfs:8888]
I0419 14:12:56.505153 filer.go:394 Start Seaweed Filer 30GB 4.17 4a5243886 at seaweedfs:8888
I0419 14:12:56.505166 meta_aggregator.go:80 loopSubscribeToOneFiler read seaweedfs:8888 start from 2026-04-19 14:11:56.504821078 +0000 UTC 1776607916504821078
I0419 14:12:56.505296 filer.go:416 Registered IAM gRPC service on filer
I0419 14:12:56.506393 meta_aggregator.go:185 subscribing remote seaweedfs:8888 meta change: 2026-04-19 14:11:56.504821078 +0000 UTC, clientId:390047446
I0419 14:12:56.507274 filer_grpc_server_sub_meta.go:411 + local listener filer:seaweedfs:8888.18888@172.24.0.2:46788 clientId -390047446 clientEpoch 1
I0419 14:12:56.507288 filer_grpc_server_sub_meta.go:163  + filer:seaweedfs:8888.18888@172.24.0.2:46788 local subscribe / from {Time:2026-04-19 14:11:56.504821078 +0000 UTC Offset:-2 IsOffsetBased:false} clientId:-390047446
I0419 14:12:57.446464 s3.go:260 S3 read filer buckets dir: /buckets
I0419 14:12:57.446498 s3.go:262 S3 read master addresses for discovery: [seaweedfs:9333]
I0419 14:12:57.446521 s3.go:270 connected to filers [seaweedfs:8888]
I0419 14:12:57.446586 s3.go:291 Starting S3 API Server with standard IAM
I0419 14:12:57.452627 filer_client.go:176 FilerClient: started filer discovery for group '' (refresh interval: 5m0s)
I0419 14:12:57.452669 masterclient.go:440 .s3 masterClient bootstraps with masters {[seaweedfs:9333] <nil>}
I0419 14:12:57.454718 masterclient.go:216 .s3 masterClient gRPC stream established to seaweedfs:9333 in 1.997825ms
I0419 14:12:57.455025 master_grpc_server.go:406 + client .s3@172.24.0.2:18333
I0419 14:12:57.455424 masterclient.go:291 + filer@seaweedfs:8888 noticed .s3 172.24.0.2:18333
I0419 14:12:57.455457 masterclient.go:291 + master@seaweedfs:9333 noticed .s3 172.24.0.2:18333
I0419 14:12:57.455487 masterclient.go:247 master seaweedfs:9333 redirected to leader seaweedfs:9333.19333
I0419 14:12:57.455817 master_grpc_server.go:421 - client .s3@172.24.0.2:18333
I0419 14:12:57.456037 masterclient.go:293 - filer@seaweedfs:8888 noticed .s3 172.24.0.2:18333
I0419 14:12:57.456067 masterclient.go:293 - master@seaweedfs:9333 noticed .s3 172.24.0.2:18333
I0419 14:12:57.457931 masterclient.go:216 .s3 masterClient gRPC stream established to seaweedfs:9333 in 1.902115ms
I0419 14:12:57.458264 master_grpc_server.go:406 + client .s3@172.24.0.2:18333
I0419 14:12:57.458660 masterclient.go:291 + filer@seaweedfs:8888 noticed .s3 172.24.0.2:18333
I0419 14:12:57.458673 masterclient.go:291 + master@seaweedfs:9333 noticed .s3 172.24.0.2:18333
I0419 14:12:57.471425 s3_sse_s3.go:379 SSE-S3 KeyManager: Generated and saved new KEK to filer /etc/s3/sse_kek
I0419 14:12:57.482746 s3.go:502 Start Iceberg REST Catalog Server at http://0.0.0.0:8181
I0419 14:12:57.482822 s3.go:462 Start Seaweed S3 API Server 30GB 4.17 4a5243886 at http port 8333
I0419 14:12:57.484377 filer_grpc_server_sub_meta.go:411 +  listener s3@172.24.0.2:34766 clientId -1171720488 clientEpoch 2
I0419 14:12:57.484411 filer_grpc_server_sub_meta.go:45  s3@172.24.0.2:34766 starts to subscribe /etc/ from {Time:2026-04-19 14:12:57.446625716 +0000 UTC Offset:-2 IsOffsetBased:false}
I0419 14:12:57.543030 master_client.go:24 the cluster has 1 filer
I0419 14:12:57.543069 filer_client.go:373 FilerClient: discovered 1 new filer(s) in group '': [seaweedfs:8888]
I0419 14:13:02.526800 master_grpc_server_volume.go:153 volume grow &{Option:{"collection":"sake","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign}
I0419 14:13:02.528026 store.go:269 In dir /data (disk ID 0) adds volume:1 collection:sake replicaPlacement:000 ttl:
I0419 14:13:02.561641 store.go:274 add volume 1 on disk ID 0
I0419 14:13:02.561845 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 1
I0419 14:13:02.562045 volume_growth.go:376 Created Volume 1 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:02.562114 volume_growth.go:389 Registered Volume 1 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:02.562159 volume_growth.go:146 wait for volume servers to join back
I0419 14:13:05.062599 volume_growth.go:146 wait for volume servers to join back
I0419 14:13:07.563654 volume_growth.go:146 wait for volume servers to join back
I0419 14:13:10.064393 store.go:269 In dir /data (disk ID 0) adds volume:2 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.097991 store.go:274 add volume 2 on disk ID 0
I0419 14:13:10.098134 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 2
I0419 14:13:10.098418 volume_growth.go:376 Created Volume 2 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.098534 volume_growth.go:389 Registered Volume 2 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.099165 store.go:269 In dir /data (disk ID 0) adds volume:3 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.131692 store.go:274 add volume 3 on disk ID 0
I0419 14:13:10.131828 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 3
I0419 14:13:10.132077 volume_growth.go:376 Created Volume 3 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.132130 volume_growth.go:389 Registered Volume 3 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.132631 store.go:269 In dir /data (disk ID 0) adds volume:4 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.165361 store.go:274 add volume 4 on disk ID 0
I0419 14:13:10.165452 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 4
I0419 14:13:10.165688 volume_growth.go:376 Created Volume 4 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.165756 volume_growth.go:389 Registered Volume 4 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.166288 store.go:269 In dir /data (disk ID 0) adds volume:5 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.199028 store.go:274 add volume 5 on disk ID 0
I0419 14:13:10.199120 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 5
I0419 14:13:10.199329 volume_growth.go:376 Created Volume 5 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.199377 volume_growth.go:389 Registered Volume 5 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.199889 store.go:269 In dir /data (disk ID 0) adds volume:6 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.232732 store.go:274 add volume 6 on disk ID 0
I0419 14:13:10.232850 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 6
I0419 14:13:10.233136 volume_growth.go:376 Created Volume 6 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.233186 volume_growth.go:389 Registered Volume 6 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.233691 store.go:269 In dir /data (disk ID 0) adds volume:7 collection:sake replicaPlacement:000 ttl:
I0419 14:13:10.266380 store.go:274 add volume 7 on disk ID 0
I0419 14:13:10.266461 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 7
I0419 14:13:10.266711 volume_growth.go:376 Created Volume 7 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:10.266846 volume_growth.go:389 Registered Volume 7 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:37.480254 lock_client.go:107 Lock owner changed from  to seaweedfs:8888-s3-metrics
I0419 14:13:54.447625 master_grpc_server_volume.go:153 volume grow &{Option:{"replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign}
I0419 14:13:54.448342 store.go:269 In dir /data (disk ID 0) adds volume:8 collection: replicaPlacement:000 ttl:
I0419 14:13:54.491931 store.go:274 add volume 8 on disk ID 0
I0419 14:13:54.492105 volume_grpc_client_to_master.go:238 volume server seaweedfs:8080 adds volume 8
I0419 14:13:54.492342 volume_growth.go:376 Created Volume 8 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:54.492395 volume_growth.go:389 Registered Volume 8 on topo:DefaultDataCenter:DefaultRack:seaweedfs:8080
I0419 14:13:54.492423 node.go:192 topo failed to pick 1 from  0 node candidates
I0419 14:13:54.492440 volume_growth.go:135 create 7 volume, created 1: Not enough data nodes found!
I0419 14:17:57.544850 master_client.go:24 the cluster has 1 filer

[Sudashiii]

The prebuilt compose file uses the prebuilt image that is created from the master branch, so you still used the old code. I merge the changes, since they should fix it and then you can use the latest pre-built image. Please close the issue if it works with the newest docker image.

[Jalsemgeest]

Okay, I can confirm that if I use the docker-compose.selfhost.yaml from the root directory it works. But if I try the docker-examples/docker-compose.prebuilt.selfhost.yaml it doesn't work still.

[Sudashiii]

Maybe there is still some caching issue, since it just takes the latest image. You could also try explicitly setting the version.

[Jalsemgeest]

I have just since used the docker-compose.selfhost.yaml and it works great.