500 Internal Server Error
-
Hello!
Today I activated your plugin in a client page hosting in One.com and it worked great. I decided to give it a try in two webpages that I have hosted on Dreamhost and in both after activating the cache the page gave me a 500 Internal Server Error.
Any idea what could it be causing it?
Thanks! Love!
-
Hi @ubuntuproductions ,
I don’t know, you should see into your PHP error log to find the code that causes the error.Let me know. If it is a problem of the plugin, I will release a fix 🙂
Hello @salvatorefresta 😊
Thank you so much for coming back to me!! Great service, I appreciate.
This is the info that Dreamhost sent over, is that any help?
This error was related to the cache plugin adding this to your .htaccess
file.
# BEGIN WP Cloudflare Super Page Cache
# The directives (lines) betweenBEGIN WP Cloudflare Super Page Cache
andEND WP Cloudflare Super Page Cacheare
# dynamically generated, and should only be modified via WordPress
filters.
# Any changes to the directives between these markers will be
overwritten.
#<IfModule mod_headers.c>
#Header unset Pragma “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
#Header always unset Pragma “expr=resp(‘x-wp-cf-super-cache-active’) ==
‘1’”
#Header unset Expires “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
#Header always unset Expires “expr=resp(‘x-wp-cf-super-cache-active’) ==
‘1’”
#Header unset Cache-Control “expr=resp(‘x-wp-cf-super-cache-active’) ==
‘1’”
#Header always unset Cache-Control
“expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
#Header always set Cache-Control “s-max-age=604800, s-maxage=604800,
max-age=60” “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
#</IfModule>
# END WP Cloudflare Super Page CacheThanks!
Hi @ubuntuproductions ,
that’s very strage, these are standard htaccess rules. What web server are you using?If you don’t want use web server rules, turn off the option Overwrite the cache-control header for WordPress’s pages using web server rules
Let me know if all works
-
This reply was modified 6 years ago by
Salvatore Fresta.
Hello again! ❤
No idea what web server we are using 😂
They commented on those lines in the .htaccess so as soon as I activated the plugin everything was working fine. I have deactivated that switcher and I will remember to do it if I use the plugin in any other domain in this hosting.
Thank you for the service and for the plugin. Love!
You’re welcome. These rules may be required if you use this plugin with other performance plugins, so please check if all works well.
On next version (4.2) I will release a fallback page caching system so you don’t need to use the page caching options of other plugins (if you desire a fallback page cache when the cache on Cloudflare expires), while you can continue to use all the other optimization options (minify css, etc..)
Have a nice day and don’t forget to drop a rewiew if you like it 🙂
Hello Salvatore! 💕
I didn’t really understand anything from what you wrote, from all the things to have in mind when building webpages this page speed optimizations seems to be the one most difficult to grab and understand to me. 😊
I was using in the page Autoptimize and Cache Enable before I installed your plugin. Is any of them redundant? Shal I uninstall any of them? Do I need to do some special configuration in Cloudfare?
This is the response I got from Dreamhost:
Thanks for your email. It’s actually not a coding conflict but a syntax
error. I’m not sure if one.com are using different Apache versions etc so
it’s difficult to assess the differences but I’d recommend contacting the
plugin developer for clarification if it is something you’d like to
continue using. If any technical specs or info is required as a result of
that, just let us know!Thank you so, so, so very much for taking from your time and energy for this. Love!
Hi @ubuntuproductions ,
the syntax is in accordance with the documentation of the mod_headers Apache module:https://httpd.apache.org/docs/2.4/mod/mod_headers.html
expr=value is available starting from Apache 2.4.10, released on July 2014. I don’t know which Apache version runs on your hosting provider :/
Ahhhh, what a strange coincidence, I just received an email fro my hosting company this morning saying that they will do some updates, right now my virtual server is running with Apache 2.2.31 and from Juni 18 is going to be updated to 2.4.25. I guess then I could activate it.
good news 🙂 welcome to 2020 😀
😂
What about Autoptimize and cache enabler? does tey work together with your plugin?
Wait the version 4.2 and you don’t need cache enabler 😉 Autoptimize works, but I love to use litespeed cache for on page optimizations
-
This reply was modified 6 years ago by
The topic ‘500 Internal Server Error’ is closed to new replies.