Title: bypassing_apache
Last modified: February 9, 2021

---

# bypassing_apache

 *  Resolved [aldikeo](https://wordpress.org/support/users/aldikeo/)
 * (@aldikeo)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/bypassing_apache/)
 * Two different hosting and different sites have the same bypassing_apache error.
   Support says the problem is in the plugin. How to treat?

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

 *  Plugin Author [Mateusz Gbiorczyk](https://wordpress.org/support/users/mateuszgbiorczyk/)
 * (@mateuszgbiorczyk)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/bypassing_apache/#post-14025205)
 * Hi [@aldikeo](https://wordpress.org/support/users/aldikeo/),
 * Thank you for your message.
 * Please read this thread:
    [https://wordpress.org/support/topic/server-configuration-error-what-to-do/](https://wordpress.org/support/topic/server-configuration-error-what-to-do/)
 *  [polyfade](https://wordpress.org/support/users/polyfade/)
 * (@polyfade)
 * [5 years ago](https://wordpress.org/support/topic/bypassing_apache/#post-14473054)
 * I’m also having this problem of `bypassing_apache`, like so many other have posted
   to this forum. Both GD and imagick are installed and support webp, png and jpeg/
   jpg. I checked my server config against the one provided in the FAQs. [https://gbiorczyk.pl/webp-converter/serverinfo.png](https://gbiorczyk.pl/webp-converter/serverinfo.png)
 * I tried both PHPv3.x and v 4.x
 * Both of the test png files for before and after succeeded too. For some reason
   my server isn’t allowing these access rules to be written to these htaccess files.
   File permissions are 644. Directories are 755. I can see the htaccess files this
   plugin has generated but there are no rules defined within them.
 * I don’t have any caching or security plugins enabled or server-side caching enabled
   for that matter.
 * I checked my wp-config and other htaccess files as well for anything that would
   prevent access to these files.
 * I’m completely dumbfounded.
 * Basically, I had to copy the htaccess files where this plugin was working from
   my local dev and add them to my shared hosting in order to get this working. 
   This might be ill-advised but it was the only way to get this working. And it
   does work without error. The files get generated and the webp type has been assigned
   to relevant images.
    -  This reply was modified 5 years ago by [polyfade](https://wordpress.org/support/users/polyfade/).
    -  This reply was modified 5 years ago by [polyfade](https://wordpress.org/support/users/polyfade/).

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

The topic ‘bypassing_apache’ is closed to new replies.

 * ![](https://ps.w.org/webp-converter-for-media/assets/icon-256x256.png?rev=2636288)
 * [Converter for Media - Optimize images | Convert WebP & AVIF](https://wordpress.org/plugins/webp-converter-for-media/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/webp-converter-for-media/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/webp-converter-for-media/)
 * [Active Topics](https://wordpress.org/support/plugin/webp-converter-for-media/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/webp-converter-for-media/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/webp-converter-for-media/reviews/)

## Tags

 * [apache](https://wordpress.org/support/topic-tag/apache/)

 * 2 replies
 * 3 participants
 * Last reply from: [polyfade](https://wordpress.org/support/users/polyfade/)
 * Last activity: [5 years ago](https://wordpress.org/support/topic/bypassing_apache/#post-14473054)
 * Status: resolved