There may be a code problem in some of the V5 changes to this but I will need to do some tests before I can be sure so that is a task for later today.
But I can explain why you are seeing what you are seeing (even if it ends up that the code is wrong)!
If you are using the popup image enlargement feature to display images, then SP needs to know the width of the image. A normal and correctly formed html image tag will include the width. If, however, the user making the post has not included the image width then we need to interrogate the image file to determine the width. So a call is made to the source image url using the php function getimagesize().
If this call fails then you end up with the message you have seen. Which probably means the server in question was unwilling to provide the data and blocked the access. This is pretty unusual which is why I asked about images from other sources.
Looking at the code however does suggest that we may be making that attempt whether the image popup function is being used or not which is most likely incorrect as if it is not being used and while knowing the image width is useful, it is not an imperative. The one good reason for doing this whether the option is being used or not is, of course, in case a user decides to turn it on at a later date as it will ensure that all images DO have the width recorded in the post data.
I suppose one good way around that problem is to continue to seek the width as we do now but not to fail it if (a) the server rejects the attempt AND (b) the popup feature is turned off.
So I will take a longer look at the code today and run some tests and make those changes if necessary and possible.