@fortunato I forgot to say that this error doesn't show up when creating a new topic and sometimes it works also in replies. The error in the NodeBB UI is the following: "stream ended unexpectedly"
6c6ff98f-95d8-4ad4-b402-b7a336cf47e7-image.png
Are you running any proxies on your PC? Google specifically.
No, I am not running any proxies. why https://ci3.googleusercontent.com/proxy/eBkkTWd9R0xVTXFAFXMUPj-95JsdcP2j3XFbLhsjSXbpDXU1BRmcx15AvHxe50LPrOv4NczWbCHSUx2ElirgyzgRu_a4pbJknjMNe7xhp4Bv=s0-d-e1-ft#http://stag-csio-forum.com/uploads/profile/8-profileimg.jpg this kind of link created in digest?
We don't do it, your mail client does.
@suraj @julian - Technically not client related - this is gmail related. The googleusercontent thingy is a image serving proxy on gmail. One of those things you have to sort of live with.
Try testing with a non-google imap client (perhaps outlook / thunderbird) I know it works on google hosted email accounts - custom domains which use the gmail service. I have not tested third party imap clients with a default @ gmail account - sorry.
So there is no solution to this problem?
@KasparTr the problem is caused by opening the emails in Gmail. Open it in other services and the image may not be proxied.
@PitaJ I cannot dictate what services my users use. Most of them use gmail so it is a problem. My email digest goes to users and the image is broken.
@KasparTr does it work on other email providers, though? It could just be that there is some kind of bad thing happening between Gmail proxy and the NodeBB thing. It could be that it doesn't work at all. I suggest testing it with hotmail or yahoo.
@PitaJ Could be, I will test it, thanks!
Althou it if weird that it just dosen't play well with the largert email service
@KasparTr I don't know what's causing it but I think it has something to do with the pound sign in the URL