ERROR: "Failed to write response: Is a directory" when trying to hit repo on 8081

[Routhinator]

After getting this setup for the first time following he quickstart - the repo closes the socket without a response, and the following error is in the logs.

Logs

aurcache_1           | [2025-09-07T21:33:52Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).

I've checked the permissions of the directories, and can see that under /app/repo/ the various arch directories are created and working - I can't firgure out why it's spitting this error for the repo port.

Compose file:

services:
  aurcache:
    image: ghcr.io/lukas-heiligenbrunner/aurcache:latest
    ports:
      - "8084:8080" # Frontend
      - "8085:8081" # Repo
    volumes:
      - /data/www/html/aurcache/repo:/app/repo
    privileged: true
    environment:
      - DB_TYPE=POSTGRESQL
      - DB_USER=aurcache
      - DB_PWD=aurcache
      - DB_HOST=dbhost
      ## HERE
      - MIRROR_RANK_SCHEDULE=0 0 2 * * 0
      ## END HERE
    networks:
      aurcache_network:
    restart: always
  aurcache_database:
    image: postgres:latest
    volumes:
      - ./aurcache/db:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=aurcache
      - POSTGRES_USER=aurcache
    restart: always
    networks:
      aurcache_network:
        aliases:
          - "dbhost"

networks:
  aurcache_network:
    driver: bridge

[Routhinator]

Oddly enough I've found that once I put it behind NGINX, if I really hammer reload - occasionally a request gets through without that error..

aurcache_1           | [2025-09-07T23:03:27Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:27Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:27Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:28Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:28Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:28Z ERROR rocket::server::_] No matching routes for GET /favicon.ico image/avif.
aurcache_1           | [2025-09-07T23:03:28Z WARN  rocket::server::_] No 404 catcher registered. Using Rocket default.
aurcache_1           | [2025-09-07T23:03:32Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1           | [2025-09-07T23:03:33Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).

Additional info in DEBUG:

aurcache_1            | [2025-09-08T15:37:33Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1            | [2025-09-08T15:37:33Z DEBUG hyper::server::server::new_svc] connection error: user body write aborted: early end, expected 9223372036854775807 more bytes
aurcache_1            | [2025-09-08T15:37:52Z WARN  rocket::server::_] Failed to write response: Is a directory (os error 21).
aurcache_1            | [2025-09-08T15:37:52Z DEBUG hyper::server::server::new_svc] connection error: user body write aborted: early end, expected 9223372036854775807 more bytes

[Routhinator]

Well - from this similar Rust related SO I can surmise that this application is expecting something to be a file and not a dir.. Hmm

[Routhinator]

Oh looking at the API for the Rust rocket server it doesn't appear to have directory listing.... 😬

What breaks in AURCache if I just bypass this and use NGINX with a proxy-cache to populate the repo directory instead? Doesn't make much sense to me to reimplement an HTTP server especially without standard dir listing and I am already running and NGINX instance for the other repos on this box.

[Lukas-Heiligenbrunner]

Hey, thanks. I'll have a look.

What breaks in AURCache if I just bypass this and use NGINX with a proxy-cache to populate the repo directory instead? Doesn't make much sense to me to reimplement an HTTP server especially without standard dir listing and I am already running and NGINX instance for the other repos on this box.

Nothing breaks in AURCache if you use nginx to serve the repo. That's basically the same what the backend does for now.
It was just easier to use the same webserver (rocket) to serve the package files than starting a seperate nginx instance. This way I could (when i find time) add package downlaod statistics and stuff like this in the future.