Hi @Christian_Terp - what device and browser is this on? It may be related to the image being served over HTTP (instead of HTTPS) and some modern web browsers beginning to block ‘mixed content’ by default.
There’s some more details, including work arounds, noted here: