bela
@Adam
Same here, we checked on two different clusters ( LSWS & OLS ) and saw similar errors in the logs journalctl -u filerd.service -f. Probably best to report this to Enhance in a ticket.
filerd[PID]: DEBUG filerd::api::fs::head: Request to check if ResourcePath { website_id: "<site-uuid>", path: "test/123/1.txt" } exists
filerd[PID]: INFO actix_web::middleware::logger: "HEAD /websites/<site-uuid>/fs/test/123/1.txt HTTP/1.0" 404 0
filerd[PID]: DEBUG filerd::api::fs::post: Request to create ResourcePath { website_id: "<site-uuid>", path: "test/123/1.txt" }
filerd[PID]: DEBUG filerd::auth: Extracting JWT token from request header
filerd[PID]: Error { kind: InvalidArgument, entity: Some(Credentials), msg: None }
filerd[PID]: DEBUG filerd_lib::error: ExpiredSignature
filerd[PID]: INFO actix_web::middleware::logger: "POST /websites/<site-uuid>/fs/test/123/1.txt?overwrite=true HTTP/1.0" 400 18
filerd[PID]: DEBUG filerd::api::fs::post: Request to create ResourcePath { website_id: "<site-uuid>", path: "test/123/1.txt" }
filerd[PID]: DEBUG filerd::auth: Extracting JWT token from request header
filerd[PID]: DEBUG filerd::api::fs::put: Checking "test/123/1.txt"
filerd[PID]: DEBUG filerd_lib::error: No such file or directory (os error 2)
filerd[PID]: INFO actix_web::middleware::logger: "POST /websites/<site-uuid>/fs/test/123/1.txt?overwrite=true HTTP/1.0" 404 0
