starred/flyimg

Fork 0

mirror of https://github.com/flyimg/flyimg.git synced 2026-04-25 09:45:50 +03:00

[GH-ISSUE #466] Broken images #780

New issue

Closed

opened 2026-03-15 15:24:38 +03:00 by kerem · 9 comments

kerem commented

2026-03-15 15:24:38 +03:00

Owner

Originally created by @jvzaniolo on GitHub (Jun 6, 2024).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/466

Originally assigned to: @sadok-f on GitHub.

Broken Images

Sorry for the short title, I really don't have a clue what's happening.

Sometimes an image is cut in half and a gray box appear in the background.

I can fix the image using the rf_1 option, but I would like to understand what's happening.

Originally created by @jvzaniolo on GitHub (Jun 6, 2024). Original GitHub issue: https://github.com/flyimg/flyimg/issues/466 Originally assigned to: @sadok-f on GitHub. # Broken Images Sorry for the short title, I really don't have a clue what's happening. Sometimes an image is cut in half and a gray box appear in the background. I can fix the image using the `rf_1` option, but I would like to understand what's happening. ![image](https://github.com/flyimg/flyimg/assets/54036572/2ec62438-8de2-4239-b9ee-dd72e913f437)

kerem

2026-03-15 15:24:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-15 15:24:54 +03:00

Author

Owner

@sadok-f commented on GitHub (Jun 6, 2024):

Hi @jvzaniolo
thank you for reporting this issue.
can you share more details about your setup?
which version of Flyimg are you using?
can you paste the endpoint here?

for the image with the gray box, can you past here the full URL of it?

thanks!

@sadok-f commented on GitHub (Jun 6, 2024): Hi @jvzaniolo thank you for reporting this issue. can you share more details about your setup? which version of Flyimg are you using? can you paste the endpoint here? for the image with the gray box, can you past here the full URL of it? thanks!

kerem commented

2026-03-15 15:24:59 +03:00

Author

Owner

@jvzaniolo commented on GitHub (Jun 6, 2024):

We're using the latest Docker image "flyimg/flyimg:latest"
The endpoint: https://img.beuni.com.br
And the broken image URL: https://img.beuni.com.br/upload/w_400,h_400,o_webp/https://proxy.beuni.com.br/api/images/products/rec2IHRZ6otqa8NCK-attyUE2bO6tH55GSI.webp

Thanks for the quick response!

@jvzaniolo commented on GitHub (Jun 6, 2024): We're using the latest Docker image `"flyimg/flyimg:latest"` The endpoint: https://img.beuni.com.br And the broken image URL: https://img.beuni.com.br/upload/w_400,h_400,o_webp/https://proxy.beuni.com.br/api/images/products/rec2IHRZ6otqa8NCK-attyUE2bO6tH55GSI.webp Thanks for the quick response!

kerem commented

2026-03-15 15:25:04 +03:00

Author

Owner

@sadok-f commented on GitHub (Jun 6, 2024):

why is the source image https://proxy.beuni.com.br/api/images/products/rec2IHRZ6otqa8NCK-attyUE2bO6tH55GSI.webp
has a Content-Type: image/jpeg but the extension is webp?
did you try the output jpeg format o_ jpg ?

@sadok-f commented on GitHub (Jun 6, 2024): why is the source image [https://proxy.beuni.com.br/api/images/products/rec2IHRZ6otqa8NCK-attyUE2bO6tH55GSI.webp](https://img.beuni.com.br/upload/w_400,h_400,o_webp/https://proxy.beuni.com.br/api/images/products/rec2IHRZ6otqa8NCK-attyUE2bO6tH55GSI.webp) has a `Content-Type: image/jpeg` but the extension is webp? did you try the output jpeg format `o_ jpg` ?

kerem commented

2026-03-15 15:25:09 +03:00

Author

Owner

@jvzaniolo commented on GitHub (Jun 6, 2024):

Yeah, this was an internal issue.
We were searching for the image with .wepb on S3 Bucket but the image was really .jpeg. The URL is dynamically generated.

Changing the output format to o_jpg works, but I'm concern that's creating another cache entry instead of fixing the problem.
Is it possible to change the image format with Flyimg? Or am I suppose to set o_ to the image original type?

@jvzaniolo commented on GitHub (Jun 6, 2024): Yeah, this was an internal issue. We were searching for the image with `.wepb` on S3 Bucket but the image was really `.jpeg`. The URL is dynamically generated. Changing the output format to `o_jpg` works, but I'm concern that's creating another cache entry instead of fixing the problem. Is it possible to change the image format with Flyimg? Or am I suppose to set `o_ ` to the image original type?

kerem commented

2026-03-15 15:25:14 +03:00

Author

Owner

@sadok-f commented on GitHub (Jun 6, 2024):

for AVIF and WebP formats, you can disable them in the config file by setting:

enable_avif: false
enable_webp: false

also Flyimg can support S3 as a storage layer, so if you have another storage endpoint, Flyimg can fetch the image and store it in s3, unfortunately it doesn't support folder structuring.

@sadok-f commented on GitHub (Jun 6, 2024): for AVIF and WebP formats, you can disable them in the config file by setting: ```yaml enable_avif: false enable_webp: false ``` also Flyimg can support S3 as a storage layer, so if you have another storage endpoint, Flyimg can fetch the image and store it in s3, unfortunately it doesn't support folder structuring.

kerem commented

2026-03-15 15:25:19 +03:00

Author

Owner

@jvzaniolo commented on GitHub (Jun 7, 2024):

I need to search for the image in two different tables on our database so we're running a node app to search for the image and store it in S3. Could Flyimg do that for me?

I'll try to disable AVIF and WebP formats

@jvzaniolo commented on GitHub (Jun 7, 2024): I need to search for the image in two different tables on our database so we're running a node app to search for the image and store it in S3. Could Flyimg do that for me? I'll try to disable AVIF and WebP formats

kerem commented

2026-03-15 15:25:24 +03:00

Author

Owner

@sadok-f commented on GitHub (Jun 8, 2024):

Flyimg can handle a custom logic for the storage, but it doesn't do that for fetching the source images.
you can keep your node app to search for the images and return the endpoint, and use the S3 storage option in Flyimg to store the generated images there.

Let me know about disabling the AVIF and WebP formats.

@sadok-f commented on GitHub (Jun 8, 2024): Flyimg can handle a custom logic for the storage, but it doesn't do that for fetching the source images. you can keep your node app to search for the images and return the endpoint, and use the S3 storage option in Flyimg to store the generated images there. Let me know about disabling the AVIF and WebP formats.

kerem commented

2026-03-15 15:25:30 +03:00

Author

Owner

@sadok-f commented on GitHub (Jun 17, 2024):

hi @jvzaniolo
any update on this issue? can we close it?

@sadok-f commented on GitHub (Jun 17, 2024): hi @jvzaniolo any update on this issue? can we close it?

kerem commented

2026-03-15 15:25:35 +03:00

Author

Owner

@jvzaniolo commented on GitHub (Jun 17, 2024):

Sorry I didn't get back to you sooner, some other things came as a priority.
I'll mark it as closed because we haven't had a similar issue since we stopped converting images to .webp, so that may be the issue.

@jvzaniolo commented on GitHub (Jun 17, 2024): Sorry I didn't get back to you sooner, some other things came as a priority. I'll mark it as closed because we haven't had a similar issue since we stopped converting images to .webp, so that may be the issue.