Hasan CALISIR

This is weird and I can not re-produce the issue on my environment. To resolve the issue, could you please connect with me via email at [email protected]? This will allow me to get the necessary details and assist you directly with accessing your server and WordPress dashboard to troubleshoot the configuration.

Once I have the required access, I can investigate the issue and provide a solution.

Looking forward to hearing from you.

Best regards,

Hello @coldrealms65,

And I notice in the Status page there is this section:
FastCGI Cache Keys
Found Unsupported

Lists this as a specific unsupported type over and over again:

$scheme$request_method$host$request_uri$mobile_device_type

Even though, for this test, my key is verified as the default:

    fastcgi_cache_key "$scheme$request_method$host$request_uri";

So something is odd….

The “FastCGI Cache Keys” section on the Status page reflects cache keys detected across all instances on the server, not just the specific WordPress installation you’re currently managing. This means if other sites or configurations on the same server use a different FastCGI cache key format, they will also appear in this section. Same true for Nginx Cache Paths section.

The Status page aggregates data server-wide, so it lists all FastCGI cache keys it finds, even if they are not relevant to your current WordPress instance. This ensures a comprehensive overview of all detected cache types across your environment.

Multiple Instances: If you have multiple WordPress instances with Nginx virtual hosts on the same server, each can have different FastCGI cache setups. The Status page aggregates all detected keys from these instances.

Tip:
You can safely ignore entries for unsupported keys if they are not relevant to your specific site configuration. For each WordPress instance on the server, ensure you set the corresponding Nginx Cache Path and configure a compatible regex that matches the fastcgi_cache_key used for that instance.

I will note, that the default test works and shows the cached page, but the dd thing is the “found unsupported” even when things appear to work normally with the default

As mentioned earlier, the “Found Unsupported” entries are part of the server-wide status check. These entries might reflect configurations from other WordPress instances or Nginx virtual hosts on the same server, each with different FastCGI cache setups. This does not affect the functionality of your current instance if it’s properly configured.

I ended up deactivating the plugin for now.

I realized where it was getting the erroneous information, It was reading from another site hosted on my server.
Executing at a level that can see other information not limited by the php user (most likely due to shell_exec) makes this whole system far far to insecure to be used in its current state so I removed it.

Have you tested this on a multi-tenent nginx system?

Sorry to hear that! I understand your concern about security in multi-tenant environments but this depend your actual web server setup.

Ensuring a secure and efficient multi-tenant environment requires correctly isolating PHP-FPM (PHP process owner or website user) and Webserver user. Ultimately, it’s in the user’s hands and depends on how the web server is configured.

• Webserver Access Control:
  The webserver user should only have read-only access to files.
• Isolation Per Instance:
  Run each site under its own PHP-FPM user for complete isolation between WordPress instances.

Please re-consider to read;
Plugin Help tab section for What is the proper PHP-FPM Nginx setup?
Main Development repostitory for Here is the short explanation of proper php-fpm nginx setup

In the NPP Status tab, there is a check for server permission isolation status to warn about current configuration.
Permission Isolation (Optional): Isolated

❗️About shell_exec

While I appreciate your feedback, it’s important to note that NPP architecture currently depends on shell_exec for efficiency. Rewriting the same functionality in pure PHP would require significant effort and time, and frankly, creating a PHP-based website crawler or bot is not on my agenda right now, especially considering there are already many plugins available for that purpose. If you have serious concerns about using shell_exec, I would recommend the Nginx Helper plugin, which is incredibly well known and easy to use.

Best~Hasan

• This reply was modified 1 year, 4 months ago by Hasan CALISIR. Reason: typo
• This reply was modified 1 year, 4 months ago by Hasan CALISIR.

I hope you’re feeling better now!

I’ve released version v2.0.8 and implemented the approaches and fixes we discussed. I’d greatly appreciate your feedback on this new release before I move forward with version v2.0.9, which will address some urgent minor changes.

Thanks for your time, and I look forward to your thoughts on the update!

Best,~Hasan

Hello @mrj0b

* Undefined constant "SIGTERM" | * Not a valid JSON response

I’ve released version v2.0.7. Please let me know if it resolves the issues you’re facing. If the issue persists, there may be a conflict with the AMP plugin you’re using.

Best~Hasan

• This reply was modified 1 year, 4 months ago by Hasan CALISIR.

Also could you check, posix extension?

php -m | grep posix

That is weird, I will try to re-produce the issue, could you tell me where do you try to Manual Purge? On Advanced tab? Or issue occurs on Auto Purge action?

@mrj0b

maybe the problem is because i disabled cron job function on my wordpress installation and replaced it with a crontab command with wp-cli that run every 5 minutes, i’ll check it later and tell you the results

I don’t think that’s the case.

Simply toggle the Auto Purge option (switch it On/Off) in the NPP settings and try again. If the error reoccurs when only the Auto Purge feature is enabled, then the issue is caused by NPP. In that case, please share the metrics from the Status tab, as well as details on how and where you encountered the ‘Not a valid JSON response‘ error.

Best~Hasan

• This reply was modified 1 year, 4 months ago by Hasan CALISIR.

Hello @mrj0b

Thank you for your feedback and sorry for my late reply.

I released version v2.0.5 that points also the issue you shared. I kindly request your feedback on the new release.

I will be releasing version v2.0.6 soon to address some urgent minor changes, so your feedback before the release would be greatly appreciated.

Best ~Hasan