X3Photo Gallery Forums

I checked myself and indeed a few images are not loading. When I check the source of the image directly, it shows this:
http://one-ten.nl/render/w480-q90/30.De ... G_2653.jpg


I tried the same image with the same resize properties here, and it works fine:


Even stranger, I tried the SAME request, with an empty ?query, and it works:
http://one-ten.nl/render/w480-q90/30.De ... .jpg?query

Different sizes works fine also:
http://one-ten.nl/render/w479-q90/30.De ... G_2653.jpg
http://one-ten.nl/render/w481-q90/30.De ... G_2653.jpg

Strange issue indeed definitely related to your server, and it's not related to Cloudflare. Seems like somehow your server has a "cached error response", as clearly the image request does work. I would recommend disabling "Always online" from Cloudflare and loading the erroneous image-request again in browser, which should render the servers error response. Likely you would need to then contact your host about that specific request, why it returns an error, while simply adding an empty ?query to the request clearly shows it works.

If you have FTP for me, I could perhaps do some additional research. I'm curious about this issue.

I tried to login and temporarily removed (renamed) the /_cache/images folder, as I suspected it was related to a cache fragment. However, it had not effect. Sorry, but this is clearly "bad apple" on the server unrelated to X3 application. Looks like it's cached a bad request or something, but there is no logical reason it should report a "timeout" ... What is the error? It should be reporting an error if there is any. You need to contact your host about this.

Summary
Here is an URL to an image that doesn't work:
http://one-ten.nl/render/w480-q90/30.De ... G_2653.jpg

No error message, no nothing, just timeout.

Just by adding a random string to the request itself, the image works fine:
http://one-ten.nl/render/w480-q90/30.De ... jpg?string

That clearly indicates that there is nothing wrong with the X3 processing script or the image itself. This is an error somehow occurring on your server based on the request.

We can even tweak the image request width +1 and -1, and it still works nicely:
http://one-ten.nl/render/w481-q90/30.De ... G_2653.jpg
http://one-ten.nl/render/w479-q90/30.De ... G_2653.jpg

Sorry, but this is something on server ... Try renaming the file?

stobbie wrote:I've tried renaming, editing in photoshop..

I logged in to your panel, and renamed the test image from IMG_2653.jpg to IMG_2653_test.jpg.

The result of the rename is that it the image works fine:
http://one-ten.nl/render/w480-q90/30.De ... 3_test.jpg

What can I say? This is some ugly bug on server level, which has absolutely no logic to it from a coding perspective. If I could have solved it for you, I would have. The issue is related to the request itself, before it even hits the X3 application. I don't know what to guess, but perhaps some firewall or caching implementation gone wrong?

stobbie wrote:you never know if an image shows up or not. But even if it would work it would be impossible to do with thousands of images.

Yes, but did you even try to contact your host? Check your server error logs?

stobbie wrote:Strange thing is that I did not have any problems with X2 on this host. I had thousands of images in X2 with a lot of visitiors, because a lot of DIY Land Rover mechanics use our project images as a reference for their own restorations.

I don't really think it's related to X2 vs X3. As you can see in the explanations above, this is some server-level request issue. To make things EVEN CLEARER:

Let's try to access the old image which we now have renamed:
http://one-ten.nl/render/w480-q90/30.De ... G_2653.jpg

Still the same bug! Even though the image does not exist any more ...  If you access an image that don't exist, for example IMG_2653ggg.jpg, you would see the error actually created by X3:


This is something on your server has decided to do based on some request (firewall or cache related I don't know). Why this did not happen with X2 is just random. The request that fails in the link above doesn't even fail from X3 ... Your host is creating a timeout on the request itself.

stobbie wrote:I'm affraid our very good google rating will drop if I'm not able to fix it n a short time.

Not sure why it would drop. X2 was awful for SEO, X3 is 100% optimized for SEO. Just because an image won't load, certainly won't have much/any negative impact on SEO. Your images in X2 weren't even detected by search engines.

stobbie wrote:Maybe I'll upload a copy to another host to compare..

It will work perfectly, at least as long as it's not the same host.

i had similar issue before, but it was because that image was too big, about 6000px

stobbie wrote:I'll try to contact my host, and if they can't help I may move to another host of put it on my vps as well.

Your host doesn't seem bad to be honest (everything else seems fine), but this issue is clearly something server-related.

laxina wrote:i had similar issue before, but it was because that image was too big, about 6000px

It's not that though. It would report an error "Memory exhausted" if the image was too big. Besides, the image works when renamed or moved.