Getting .htaccess couldn’t be found on your server error

Hi @frappeweb,

I’m not sure why you are getting that message, since there is no change in regards to the .htaccess settings with the latest version.

Can you run a Diagnostic test (Powered Cache -> Misc -> Run Diagnostic) to make sure the .htaccess file exists in the correct place?

Besides this notice there doesn’t seem to be any issues, except that CSS on WP Admin login page is broken.

Can you provide a screenshot for this?

Regards,

Hi @m_uysl,

I waited until I got the error again, and then ran Diagnostic test just as you recommended. I found something weird.

For some reason Powered Cache is looking for .htaccess file in /public_html/wp-admin/ folder (where it doesn’t exist). Please see screenshot here.

When I purge all cache and flush Memcache via cPanel, then Powered Cache properly looks for .htaccess in /public_html folder.

When this error occurs I also get this dashboard message (see screenshot), and WP Login page CSS appears to be broken (see screenshot).

Hope this helps in debugging.

Hi @frappeweb,

It seems somehow get_home_path() returns the wrong path. Could you check the configuration files if there is the same WP_CACHE_KEY_SALT used for different wp installations? The problem looks relevant to the persistent object cache.

When I purge all cache and flush Memcache via cPanel, then Powered Cache properly looks for .htaccess in /public_html folder.

You can turn off the automatic .htaccess configuration to avoid that message, but it doesn’t fix the root cause of the problem.

And the CSS problems with the login page might be related to this too. Once the internal functions return to the wrong path, it causes such a mess.

Could you check that everything works when you turn off the object cache?

Hi @m_uysl

We only have one WP installation on this particular hosting, and our wp-config.php has no defined WP_CACHE_KEY_SALTconstants.

There is only define( 'WP_CACHE', true ); // Powered Cache constant.

When we turn off the object cache everything appears to be working normally.

Is there a chance that the Memcached server is shared with other applications?

The problem is data corruption when fetching it from the persistent object cache backend. (Memcached server)

Unfortunately, I can’t help much more on the server-side debugging, but I highly advise checking how does cPanel allow to run Memcached.

Hi @m_uysl,

we use shared hosting, so your suggestion makes a lot of sense. There is probably some issue with the way how our Memcached server works. We will contact our hosting administrators and examine this issue with them.

I’m glad that we determined that Powered Cache is working properly.
Thank you very much for your time and support.

Hi @frappeweb,

we use shared hosting, so your suggestion makes a lot of sense. There is probably some issue with the way how our Memcached server works. We will contact our hosting administrators and examine this issue with them.

Yes, it is better to ask the hosting provider. If the shared memory is accessible to all users, it would be a potential security risk as well. So, I’d recommend running the Memcached/Redis in the container at least (if it’s available)

I’m glad that we determined that Powered Cache is working properly.
Thank you very much for your time and support.

Happy to help. It would be great if you could leave a review if you are happy with the Powered Cache overall ??

Regards,

• This reply was modified 2 years, 2 months ago by Mustafa Uysal.

Happy to help. It would be great if you could leave a review if you are happy with the Powered Cache overall ??

Of course! Thank you again for your help.

Thanks for the kind review.

Cheers,