Marko Vasiljevic

Hello,

Thank you very much for reaching out and for your efforts in translating the W3 Total Cache.
Please drop us a note via the plugin in Performance>Support, or via the website contact form.
Thanks!

Hello Matrin,

I am sorry about the issue you are experiencing and I am happy to assist you with this.
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server while acting as a gateway or proxy, received an invalid response from the upstream server.
YOu’ve mentioned that the server capacity is reached, so you may want to check the /cache/ folder and delete the content (don’t worry, the files will be cached again) if W3 Total Cache is active
Make sure that if you are caching to disk to disable Object Caching and Databased Caching as it’s not recommended to use those options if caching to disk.
Every 500 error should be logged so I would advise enabling wp_debug and checking the error log once, and if the error occurs again.

Hello John,

Thank you for your feedback.
As I can see the only problem is with the video on the Home page. I’ve checked the source and I can see that it should be style=”width:100% so that is strange indeed.
I’ve also checked the website bypassing the cache and it does not have any difference.
Have you tried disabling W3TC to confirm if the problem is related to our plugin?
Thanks!

Hello Libby,

Thank you for the information.
I’ve checked your website and it’s loading just fine and the testing results look good.

Can you please share what you are seeing?
Thanks!

Hello Michael,

Thank you for reaching out and I am happy to assist you with this.
1. Yes, W3 Total Cache does work with IMH nginx reverse proxy caching.
2. IMH Nginx is controlled in cPanel, however, it cannot be purged via W3 Total Cache.
3. I am not familiar with the plugin you are referring to, so Ic can not suggest it for this use case.

This being said, if you want to purge the IMH Nginx proxy, you need to do this via the IMH Control panel
I’ve opened a Github issue for this and we may add the ability to do this via W3TC.

Thank you!

Hello Brian,

Thank you for the information and I am glad everything is working as expected.
Yes, you can backup the settings:
1. Download the .json file in Performance>General Settings, scroll down to Import/Export settings and click on Download to Export Configuration.
2. You can make a backup of wp-content/w3tc-config/master.php

Thank you!

Hello Brian,

Thank you for reaching out and I am sorry about the issue you are experiencing with W3 Total Cache.

This is a very strange issue to be related to W3 Total Cache, and I am not quite sure (the first time I am seeing this kind of issue) what may be causing this.
Potentially, some cookie was cached in the browser or the Page Caching was not disabled for logged-in users.
I would recommend removing the plugin and re-install:
3. Check .htaccess File (make a backup)
W3TC will create many directives in the .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
1. Delete wp-content files and folders
– cache folder
– w3tc-config folder
– object-cache.php (if exists)
– advanced-cache.php (if exists)
– db.php (if exists)
– upgrade folder
– delete w3-total-cache folder in wp-content/plugins/ (the folder you renamed)
2. Delete Cached Files from CDN (if using CDN)
Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
3. Go to your wp dashboard and re-install W3 Total Cache

Once the plugin is re-installed make sure that when you test the behavior after enabling the settings one by one, and make sure that caching is not enabled for logged-in users.

Let me know if this helps!

Thanks!

Hello,

Thank you for the information.
Let me double-check this and I’ll get back to you once I have more details.
Thanks!

Hello Kiril,

Thank you for the information.
It’s not recommended to use the Disk Caching method for Object Caching and Database Caching especially if you are on a shared server. SO you should consider using Redis or Memcached. Please note that you need to install PHP Redis extension or PHP Memcached extension for the W3 Total Cache to recognize them and make them available in the plugin settings.
The error you are referring to suggests that there is an error in the query. Disabling Database caching should solve the problem, and you should also try to purge the database cache and check the MySQL table.
I hope this helps!

Hello Dan,

Thank you for using W3 Total Cache Pro.

Enter the license key in Performance>General settings, Licensing sub-box, license field, verify the license with the “verify license button” and save all settings.

W3 Total Cache Pro should be active after these steps!

Thanks!

Hello Kiril,

Thank you for your feedback.
Just to confirm, the error occurs once you downgraded the PHP to 7.2?
Can you please confirm if you are using OC and DB Caching and caching to Disk?
Thanks!

Hello Kiril,

I’ve checked the phpinfo.php and the PHP version is Version 7.4.25 and as I can see your website is working as expected.
Can you please confirm if you are still experiencing the issue?
Thanks!

Hello Gabriel.

Thank you for the information.
Well, this is a strange issue, to say the least.
Can you please go to Performance>Browser Cache, re-enable the Gzip compression in the General sub-box and save all settings. Then, disable the Gzip compression for each sub-box individually (HTML&XML, JS/CSS, Media, and other files), save all settings and purge the cache after each one is disabled, and see which one specifically is causing this and if that one also causes the login button to disappear??!
Do you have any other plugin that may be setting the gzip compression or possibly zlib?
Thanks!

Hello Kiril,

I am sorry about the issue you are experiencing with W3 Total Cache when upgrading the PHP version and I am happy to assist you with this.
It seems like a broken config JSON file. Are you able to download the json (Performance>General settings>Imort/export settings),
Make sure to check wp-content/w3tc-config/master.php and see if the file is broken.
If you added define( 'W3TC_CONFIG_DATABASE', true ); to wp-config.php and did not export the config settings before that, possibly the file is now broken when you try to download it.
Potentially you need json_decode installed/enabled.
W3 Total Cache doesn’t work without json_encode and json_decode, and errors like that may show up when those functions are not defined, which means either the JSON extension is not installed/enabled or it doesn’t work.
He should check the output of phpinfo(); for something similar to this:

Create a phpinfo.php in the root of yoru website and add the following line of code:

<?php

phpinfo( );

?>

Once this is done, make sure to open your website https://yourwebstie.com/phpinfo.php and check the json support and version as shown in the screenshot.

As for the questions regarding the license, please contact us directly via the plugin in Performance>Support>Sales so I can share the bulk licensing plans we have to offer at the moment.

I hope this helps!
Thanks!

Hello,

Thank you for the information and I am glad that the issue is resolved.
Most likely once the plugin(s) were updated the cache needed to be purged.
Thanks!

Hello Kobi,

Thank you for reaching out and I am happy to assist you with this.
As I can see the W3 Total Cache is enabled on your website and I can see that the slider on the homepage is working.
Can you please confirm if you are still experiencing the issue?
If you are still experiencing the issue, can you please try to disable Minify in Performance>General settings, save all settings and purge the cache and see if the issue persists?
Thanks!

Hello Mark,

Sorry for the late reply I was trying to replicate the problem.
We will do our best to set everything up. There is absolutely no reason why this can’t work, we just need to dig a little bit deeper to find out what may be causing this.
So you can go forward and purchase the Performance Audit solution so we can schedule this.
Thanks!

Hello David,

I a sorry about the issue you are experiencing and ai m happy to assist you with this.
You can use User Agent Groups in W3 Total Cache for this. In Performance>Cache Groups you can create a group of user agents by specifying names in the user agents field. Assign a set of user agents to use a specific theme, redirect them to another domain, or if an existing mobile plugin is active, create user agent groups to ensure that a unique cache is created for each user agent group. Drag and drop groups into order (if needed) to determine their priority (top -> down).
You can enable default groups (Tablet and Phones). Select your theme from a drop-down menu, save all settings and purge the cache.
Let me know if this helps!
Thank you!

Hello Mark,

You are most welcome and Thank you for your reply.

I would be willing to do that if you can guarantee that it will actually work with the technologies we have in place.

I cannot guarantee anything because I cannot guarantee anything. Simply because I need to have access to everything in order to be able to check and confirm.
However, let me make some more tests and I’ll get back to you soon with more information.
I’ve seen the W3TC + Bitnami configurations that are working excellent, I just need to investigate more why the AWS test fails.
Please give me some time to check some more things and I’ll get back to you once I can share more details.

Thanks!

Hello Mark,

Thank you for yoru feedback and I am glad I was able to help!

The notification about CDN via Amazon being currently disabled means that the CDN is not enabled in Performance>CDN. You do not have to enable it before setting up but you need to choose the CDN type method which as I see you already did. So the notification will be gone once the CDN function is enabled.
The first thing that you should do is to remove https:// from the AWS URL in the Replace hostname with the field so it should look like this for example: d2z677rcp2alwr.cloudfront.net

As for permissions, the wording there is a bit strange. So what you did is basically deny permissions by setting the last two to “On”. I hope this makes sense.

Please let me know if this helps!

Thanks!