owncloud / owncloud/ocis

Tall images fail to load with Internal Server Error (500)

Open
#12,399 4 comments 0 reactions 0 assignees View on GitHub
Type:Bug
Dominant language
Go
Stars
2.1k
Forks
274
Avg merge
2d 2h
Merged PRs (30d)
106

Description

Tall .jpg images (e.g., with size 540 x 5899/aspect ratio = 10.92, 4.5MB) fail to load in ocis 8.0.1 (generate 500 errors). All other normal sized images load properly. I've reviewed, https://github.com/owncloud/ocis/issues/12313, https://owncloud.dev/services/thumbnails, and https://github.com/owncloud/ocis/issues/10589. I've also tried various fixes (Docker) without success including:

- THUMBNAILS_MAX_INPUT_WIDTH: "16384" and THUMBNAILS_MAX_INPUT_HEIGHT: "16384"
- THUMBNAILS_MAX_ALLOC: "0"
- THUMBNAILS_TYPES: "example/nonexistent"
- OCIS_EXCLUDE_RUN_SERVICES: "thumbnails"
- THUMBNAILS_RESOLUTIONS="16x16, 32x32, 64x64, 128x128, 1080x1920, 1920x1080, 2160x3840, 3840x2160, 4320x7680, 7680x4320"
- THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE="100MB"

I believe this should be considered a bug and not a feature request. While I accept #10589 was closed in 2024, I believe it should be revisited. A file server that errors out in 2026 when trying to serve perfectly valid files is not functioning properly. At minimum, rather than erroring out with an Internal Server Error when a thumbnail is presented or the viewer used, ocis should simply open the browser with the file in raw format when clicked on. Sending these errors suggests to users the file is corrupted (when it downloads properly and then can be viewed locally - which they would never know based on the file viewer) or there's a server problem that has to be reported to administrators (only to be told "working as designed"). Please reconsider.

## Setup
Debian 12 LAMP
Docker image: owncloud/ocis:8.0.1

Contributor guide

Open the contributing guide

Research direction

Start with the thumbnails service described at owncloud.dev/services/thumbnails and reproduce the 540 × 5899 JPEG case on the documented ocis 8.0.1 Docker setup, comparing it with issues #12313 and #10589. Trace where the request becomes a 500 and determine the expected handling for valid tall images; done means the viewer no longer returns an Internal Server Error and the intended fallback behavior is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.