fast-cgi cache is the important page cache method and aaPanel author even did not give the solution for two or more websites on this thread. Poor aaPanel. I will stop to try aaPanel here.

2 months later

aaPanel_Jose This post was very helpful. I did some modifications and finally managed to set fastcgi on multiple websites.

a month later
7 days later
6 days later

is the Nginx Helper wp plugin necessary for fastcgi cache to work or it's just for the purge cache to work? because I do it manually anyway

7 months later

Hi, I did follow your instruction and it worked, thanks for the tutorial.
But, I got a problem that is when I enable "Anti-XSS attack (Base directory limit)(open_basedir)" feature for the website, I can't do "Purge Cache" from the Nginx-Helper plugin, there was no-showed error, I clicked on it, and I check the cache folder in the server, the cached files were still there.
"Purge Cache" works well when I disable "Anti-XSS attack (Base directory limit)(open_basedir)".

So, is there any solution to that? I want to enable "Anti-XSS attack (Base directory limit)(open_basedir)"

    This doesn't work if Wordpress is in a subdirectory, what should be modified for it to work?

    aaPanel_Kern Thank you! it works well now. 😀

    I want to share my work here.
    I did update the file: /www/server# vim panel/class/panelSite.py

    As you can see in the picture, I added /dev/shm, /dev/shm is my cache path.

    Do not forget to restart the panel to apply your change.

    4 months later

    aaPanel_Kern

    I had added the headers in site config. Here are the headers that i added in site config. Without NGINX cache (NGINX Helper) its working fine.
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Frame-Options "ALLOW-FROM *";
    add_header X-Content-Type-Options "nosniff" always;
    add_header Referrer-Policy "strict-origin-when-cross-origin";
    add_header Permissions-Policy "geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()";
    add_header Content-Security-Policy "upgrade-insecure-requests";

    Permission, referral and content security is what having problems.