• Resolved swinggraphics

    (@swinggraphics)


    Frequently get “HTTP Error” during upload to a post, and “Internal error Gateway Timeout” during bulk compressing.

    Waiting while all sizes of one image are compressed is slow enough, but completely untenable with multiple images. It’s made infinitely worse when they don’t even work because of the “HTTP Errors”. Execution time is already set to 60 seconds, and I’m definitely not increasing that. Upload should happen as normal, and then optimization happen in the background with cron or something.

    In another thread TinyPNG says the “Internal error Gateway Timeout” is caused by their server, so I guess it just requires a few tries until it works. In my experience today, it seems this error will show up on the bulk processing page, but the items appear complete in the Media library, so maybe the error lies elsewhere and the message shouldn’t show at all.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author TinyPNG

    (@tinypng)

    If you have many image sizes configured and these images are large in size as well, then at the moment it can take longer than 1 minute to compress all image sizes. If your execution time is set at 60 seconds, then you will indeed receive errors like the one you’re getting if it doesn’t finish compressing your image sizes within that time frame.

    At the moment, the only remedy would be to limit the number of image sizes you have compressed, or to increase the execution time. Generally, like you mentioned, retrying it often works as well.

    The error can definitely occur both in the bulk compression tool as well as with regular image uploads. If you don’t see the error in the media library, and the images for which you received an error are completely compressed in your media library, then they were in fact compressed correctly. Are you on the latest version of the plugin (2.2.6)?
    The errors are definitely caused by something breaking the connection between your server and the Developer API. In many cases it’s caused by a relatively low execution time, but there can be different reasons for the connection to break.

    In any case, we understand that for certain configurations (large images with many image sizes and relatively short execution time) the plugin might not work optimally. Hopefully we can address that in a future update. Thanks for your valuable feedback!

    Plugin Author TinyPNG

    (@tinypng)

    We upgraded the infrastructure and changed servers, the gateway timeouts and errors should be a thing from the past.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Avoiding error messages’ is closed to new replies.