I'm using Drupal with CiviCRM 4.7.30 (but this issue also affected 4.6) on Nginx & Debian

I have a custom field used for images. Images are uploaded and stored correctly (when copying the image directly from the server it looks good), but when viewed or downloaded via /civicrm/file? the image is broken.

Using a hex viewer to inspect the files I've found that CiviCRM is adding '0A0A' to the start of the file (see attached screenshot)

screenshot of hex viewer showing 0A0A

Has anyone experienced this? Could this be an Nginx or Php issue rather than Civi?

thanks, L

  • You state both CiviCRM versions have the same problem. Probably something in de used technology stack like PHP and Nginx. Maybe you can add the versions. Another test is trying to recreate the problem on the CiviCRM test server dmaster.demo.civicrm.org . Mar 22, 2018 at 9:16
  • The issue did begin after a point release upgrade for 4.6, and I held out hope moving to 4.7 would fix it. I will do a bit more server digging and update this question if I find anything
    – Leckie
    Mar 22, 2018 at 12:07


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.