Avatar generation does not work

[realies]

Using latest stable Nextcloud with the latest container image and upon creation, user avatars look like

Nothing related in the logging section of Nextcloud

[ajayramaswamy]

I had the same thing happen to me, and I fixed it by using the nginx config from nextcloud.com, over time the location setting for various bits have changed

[thelamer]

@ajayramaswamy can you post a working config, I just tried out their current one with some slight pathing mods and I get the same results as @realies

[ajayramaswamy]

https://paste.fedoraproject.org/paste/6iuFD-sWrndENZg5QsUq~g

or

https://paste.fedoraproject.org/paste/hRh5TAxKK3ayQoJheCAXoA

[thelamer]

@ajayramaswamy thanks for the info, will get this tested.

[thelamer]

@ajayramaswamy I still get the error with these configs, and there is nothing logged. Are you sure you made no other modifications ?

[ajayramaswamy]

You will have to comment out access_log off; on lines 142, 148 etc to see logs

if the avatar is there then the log entry will look like this

"GET /nextcloud/remote.php/dav/avatars/myusername/128.png HTTP/2.0" 200 1194

so the next point of debugging s to see if the file exists at that path

[thelamer]

@ajayramaswamy files are present and I have logs enabled across the board. It is just that the files look like they are reported in this issue, tiny white box and a background.

Makes me think we are missing some kind of image manipulation dependency. Do yours look normal?

[homerr]

Hi @ajayramaswamy could you update this please

[thelamer]

I have dug deep into this and I am unable to find a solution, the only difference between our env and the official container with the most recent modification I made here #87 is dependency versions. This might simply be a side effect of using Alpine system packages for PHP and its deps.

[neckos]

I have the same issue on Alpine.

[CHBMB]

@thelamer Looks like the issue has been found by another Nextcloud container author.

crazy-max/docker-nextcloud#14 (comment)

https://github.com/crazy-max/docker-nextcloud/blob/363005714646a29bea09405371d59915ff8cd0d2/Dockerfile-13#L69-L71

[thelamer]

Yeah just tested GD from edge locally to confirm, it looks like v16 fixes this upstream so when we have a new version we can close this out.