The images is generated after at the first load of the page, i think is normal behavior, but the page is not supposed to waiting request of generating image for loading in browser ?
For another testing, i have deploy on a VPS instance with same configuration (Nginx + PHP 7.2) That work correctly.
My problem is on my Rasberry (Using for devlopement) with same configuration (Nginx + PHP7.2), From your last message, i have verify the access rights on directorys, i have always the problem after update user / group on directorys.
Do you think 1GB on rasbery can be is the problem ?
This afternoon i go compare Phpinfo on Rasberry and the VPS instance, because except the OS i don’t see where is difference configuration for this problem.
I think you can also go through the media folder and use the information in the .json files in the .jobs folders. All information about intended thumbs should be there.
A bit late, but my experience is hardly related and the solution might be useful for others, too.
I experienced that medias served for the very first time were “polluted” with a preceding newline character. Amongst others, this lead to broken image files served with a 200 HTTP Code . Due to caching headers sent by my provider’s server, these files we not reloaded for some time and the broken images were used instead.
The superfluous newline character was introduced by one of my plugin’s files starting with a newline followed by the <?php tag. Removing the newline solved the issue.