Search results

How can I remove the default files and directories from Plesk when a new domain is created? The css, img, test directories and the index.html and favicon.ico? I want httpdocs to be blank when a domain is created as WP is auto-installed.

Oh wow, I totally forgot .fcgi even existed. Yep, I think it should be removed. I think the last time I saw a .fcgi script was in 1998, lol.

This doesn't have anything to do with PHP with FastCGI?

I'm confused by this reply. Nginx cache is loaded from the disk but stored and served from memory. It should not be slower than Redis?

Is there a mailing list I can get on for announcements?

What day this week do you think the next update will be?

Excellent - no problem at all. Thanks for the fast response!

That's correct. WordPress is installed but the plugins are not installed. Tried on 4 different domains, 3 different Service Plans and 3 different WordPress Sets including creating a brand new set. Plugins are not there even 2 hours later.

I edited the WordPress Essentials set to add some plugins. Have it set to install WP under a service plan with that Set. Upon WP install it is only installing Akismet and Hello Dolly (the latter I removed from the set). Also tested other untouched sets on other service plans and they don't work...

Further has revealed that I'm now getting a HIT in Chrome, but a BYPASS in FireFox. Seems due to the way the different browsers handles the Vary header. Found it discussed in varnish: Varnish acts differently on different browser, why? So looks like an Nginx config issue.

Any solution for this on Plesk? Default should be to cache everything and add cookies not to cache. Or at least have the option. There is a whole Bypass section which is kind of superfluous as Bypass is the default behaviour. Still would like to know why I'm still getting the BYPASS with no...

Been playing around with it and added all cookies and still getting a BYPASS. Request Headers: Accept text/html,application/xhtml+xm…plication/xml;q=0.9,*/*;q=0.8 Accept-Encoding gzip, deflate, br Accept-Language en-US,en;q=0.5 Authorization Basic YmxvZ2Rldjo0cnMkemVCbG5kVmY4QTVr Cache-Control...

Where would you put that code? Little confused there. But going back to the overall function, I don't understand why Plesk would add a cache that simply won't work on 99% of websites. Is it just marketing? "Hey we do microcaching (you just can't use it without a degree in computer science).

Problem is 99% of sites use cookies. Therefore this Nginx caching is not going to work with most sites. Surely a switch to cache all that activates "proxy_ignore_headers" and then a field to add cookies not to ignore would be more useful? Most cookies can be cached. Just some cookies like those...

I was just hoping that someone on this forum had already done the heavy lifting and there was an easy walkthrough somewhere. Due to how Plesk overwrites anything not templated I think it would be risky to travel into that uncharted territory.

@trialotto thanks for the input. Do you have any resources you could point me to in regards to fine tuning Nginx?

I was just putting W3TC etc as a comparison. By far the fastest solution I have found so far is the Redis Page Cache plugin (with Redis installed obviously). I was just hoping that fastcgi/proxy_cache would be as fast

So I've been doing some extensive testing. Two domains, same wordpress theme, same server. First of all, this new Nginx cache. In Nginx settings if you deactivate the 3 options in "Return stale cached records" you will be on pure fastcgi_cache (Nginx) or proxy_cache (Nginx/Apache). On one...

@IgorG So I'm leaning towards just using pure Nginx with PHP-FPM. If using this server config surely it should be easy to activate fastcgi_cache for all domains? Any tutorial for that?

Hi Igor, Redis does work and it's pretty simple but it's not an out-box-solution. For Wordpress hosting it requires the Redis Page Cache plugin. Which is fine. It does also require symlinking the advanced-cache.php from inside the plugin folder to wp-content which of course requires SSH access...