Regenerate not working – Server Configuration Error

  • Resolved captainproton

    (@captainproton)


    4 years, 3 months ago

    I have been using Webp-converter-for-media for a few months without issue.

    I check for plugin updates daily and this morning I updated to version 1.4.2. The site is working fine but I cannot use the ‘Regenerate’ function.

    I have a Server Configuration Error

    Your server uses the cache for redirects. The rules from .htaccess file or from Nginx configuration are not executed every time when the image is loaded, but the last redirect from cache is performed. With each request to image, your server should execute the rules from .htaccess file or from Nginx configuration. Now it only does this the first time and then uses cache. This means that if your server redirected image to WebP format the first time, it does so on every request. It should check the rules from .htaccess file or from Nginx configuration each time during request to image and redirect only when the conditions are met. Disable server cache for redirects. Please contact your server administrator.

    _____________________________________

    Nothing has changed in the server configuration. It has remained constant for at least the last month. The plugin has been working and the regenerate function has always worked.

    I have use a reverse proxy setup with Nginx on the front end and Apache on the back end. Both are on separate machines.

    All .htaccess files are as suggested in another thread with the same error message. Their fix eventually turned out to be an issue with a proxy and name server changes. That doesn’t apply to me as I have my own name servers and all servers are physically located here with me. No proxies, except for Nginx.

    I also took out the caching directives relating to webp. Still no change.

    I eventually opted for a temporary fix and disabled the error checking, related to caching, within the webp code.

    That solved the problem. Regeneration completed successfully and the site is working fine after clearing the Nginx cache.

    It would seem to me there is something wacky going on with the plugin. As I’ve said, everything has been working for months and the server config has been unchanged. The only difference was the plugin update to version 1.4.2.

    I have half a dozen sites running the plugin and don’t look forward to my code mod for each of them.

    Any help would be appreciated.

Viewing 5 replies - 16 through 20 (of 20 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    @captainproton Thank you very much for your help. Ultimately, there is no other solution, because you redirect to WebP for one browser and not for another. When using the cache, this verification is not performed every time.

    Same issue. Here’s a screenshot. https://ibb.co/4sLPGNJ
    I’m not a tech person. I’m a server is apache. I’ve just found and installed this plugin but no luck seeing this in action yet.

    Mine is a Test and learning site. Gzip is not enabled from Cpanel. No cache plugins are active. Had shortpixel installed but images were not converted (disable now). Have the Unsplash plugin installed for some images which pulls images from their own CDN. And I have SVG support plug-in installed.
    Not sure if these are important in this context, just thought to let you know.

    Thread Starter captainproton

    (@captainproton)

    @mktk54 I think I read on the faq for this plugin that it does not work with CDNs. I could be wrong and the plugin author will correct me if I am.

    Yes, surely that can be trouble. I’ve uninstalled the official Unsplash plugin which links the images with their CDN. Another unofficial but even better plugin is there which copies the images directly to the media gallery of WordPress. Less worrisome.

    “WebP Converter for Media” sounds amazing for its features. And I’d wait for this to work for me. Thanks to the developer.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Regenerate not working – Server Configuration Error’ is closed to new replies.