Support » Plugin: Images to WebP » Image converting

  • Resolved Tony Franco

    (@tony-franco)


    Dear Sir,

    Thank you by this plugin and last update!

    Please, i´m getting an 403 error on converting images:

    https://ibb.co/cw0p0ch

    Also, i have a doubt at nginx.

    After enabled hotlinking protection at nginx, the webp images displaying stopped to work, so i disabled hotlinking protection, it returned to display webp images on browser. Do you know what can be?

    Thanks and Regards,
    Tony

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author kubiq

    (@kubiq)

    Hello,

    403 means forbidden in general
    https://en.wikipedia.org/wiki/HTTP_403#Substatus_error_codes_for_IIS
    it can be locked folder, missing images, or some strong security plugin protection… hard to say… it’s best when you check your FTP… take a look what files don’t have webp a then try to figure out why… maybe image file is corrupted or there is very strict CHMOD… I’m afraid I can not help you more here

    or is this happening to every single folder? And you’re not able to convert any image?

    about hotlinking – sorry again, but you have to ask your server provider or some nginx administrator, because I’m more apache user than nginx… i’ve tested my plugin on nginx, but i never wrote any other nginx rules except these ones for my plugin…
    there should be no connection with hotlinking… it’s about serving different content for different file, so maybe just try a little bit different syntax, or maybe on nginx the sort order of rules is important like on apache?

    Thread Starter Tony Franco

    (@tony-franco)

    Hello @kubiq

    Thanks by your return.

    I tried to deactivate all other plugins, then try again but didn´t work, also changing the chmod of images, didn´t work either… So returned to previous version of plugin, and returned to work… testing the same files.

    About the nginx, thanks i will look for solutions and different order of rules to test!

    Regards,
    Tony

    Plugin Author kubiq

    (@kubiq)

    ok wait, so older version works for you?
    What version? 1.8 or 1.7 ?
    I will investigate this, just let me know which version is working for you

    Thread Starter Tony Franco

    (@tony-franco)

    I´m using now 1.8:

    https://ibb.co/WxZj6nH

    Thanks!

    Plugin Author kubiq

    (@kubiq)

    wow, that’s weird, because there were only some security adjustments in 1.9, but obviously one of these things is breaking it on your side
    can you check browser console (F12) during conversion and debug.log on your hosting if you can see anything wrong?
    you can use pastebin if there is longer content in debug.log
    is your website standard setup and installation or it is something more special?

    Thread Starter Tony Franco

    (@tony-franco)

    Hi @kubiq

    I have tested at another nginx instance and the new version of plugin (1.9) worked!

    The first nginx instance that didn´t work has a different server block with more rules for example using fast cgi cache and other protection rules..

    I´m sorry to disturb you… i will have to discover what part of server block is blocking the work of plugin… so i will use 1.8 for that instance for now… when i find the reason i post here..

    Thanks and Regards,
    Tony

    • This reply was modified 2 months, 4 weeks ago by Tony Franco.
    Plugin Author kubiq

    (@kubiq)

    ok, thank you very much

    Thread Starter Tony Franco

    (@tony-franco)

    Hi @kubiq

    I have tested that server block excluding some rules, but at the end didn´t work..

    So compared the versions and changed the function 1.9 convert_old_images by the 1.8 version at images-to-webp.php, and it returned to work… that happens only in this instance i don´t know why, at another worked well…

    I´m sorry to disturb you, next weeks i will deploy a new instance and check if it repair.

    Thanks by your plugin!

    Regards,
    Tony

    Plugin Author kubiq

    (@kubiq)

    hm,
    then it’s probably some problem with $folder or $secure_path variable … it’s probably somehow misinterpreted in your configuration or server…
    can you use error_log function to store these 2 variables in debug.log and show me how it looks like? You can censure some parts if needed…
    Something like error_log( print_r( array( 'folder' => $folder, 'secure_path' => $secure_path ), 1 ) ); and you can put it before/above if( substr( $folder, 0, $secure_path_len ) === $secure_path ){

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.