Add Google pagespeed integration
The PageSpeed module is now precompiled with nginx in Plesk Onyx 17.9 Pleview – https://docs.plesk.com/release-notes/onyx/change-log/#contents-179-preview6
Giancarlo Di Massa commented
+1. Any ETA on this?
we need to know ETA on this.
Come on Plesk, it's been 5 years we are asking for this very useful integration
Any ETA on that?
ngx_pagespeed is needed as well! Thanks
mod_pagespeed for nginx pleaaaaaaase
Any update on this? I would really like mod_pagespeed for Nginx with plesk.
True. By adding the "non-essential but very useful" stuff, plesk adds more value to its product. Plesk is already a very good bridge between noobs and super-pro-freaks. I would never build my own nginx from source - way to complicated for me. Same is true for the mod_pagespeed. BUT with plesk I have my Ubuntu 16 with nginx and https2 up and running passing all benchmarks from google and others with excellence. I am really thankful for plesk - but still: PLEASE GIVE US ngx_pagespeed ;-)
Tozz's point is from an implementation's point of view.
Plesk is already far beyond managing merely the distribution at hand.
By not forcing their users to build Nginx/Apache from source for features that are in demand now, they would be able to properly support it as they all would have that same enhanced package.
Hmmm - I can understand your point. But I am still having a different opinion ;-)
I don't mix things up. The point is that Plesk relies on distribution supplied software, such as Apache, Nginx, Dovecot, Postfix and what not. Plesk's job is not to extend services that eg. Debian deliveres with extra modules or addons. Sure, they _could_. But I think they shouldn't! This is like asking your gas station to fit a bigger tank in your car. Its not their job. Doesn't matter if its HTTP/2, PageSpeed or whatever extra plugin
If you really want to you could just as easily use a backported version of eg. Apache. Or simply wait for a new release of your distribution. There are also plenty of manuals available on how to install PageSpeed yourself.
Another issue is that these third-party modules cannot be relied on. For example, mod_spdy in the time used a staticly compiled version of libssl. Then when all the OpenSSL fun started, none of those mod_spdy installations got patched, even though the distribution did upgrade/patched openssl/libssl. Then, Google abandoned Speedy completely and more systems remained insecure as no patches were released.
lets not forget, the same rants here about "WE NEED SPDY NOW!" are not that long ago.
Plesk is a Control Panel. Basically a GUI to generate configuration files. Let's not make it the same mess as DirectAdmin is for example, with all the custom compiled software with all the flaws (eg. installing 2 versions of libssl, where default Debian tools complain about missing functions).
With the way it is now you can rely on your distribution for security updates. We should not be having to rely on Parallels for software patching other than Plesk itself.
PS: HTTP/2 isn't running on Debian 8 machines yet. Could be that another Plesk supported OS does have it.
That is absolutely not true. Plesk could easily integrate mod_pagespeed into nginx. Sure it is possible to solve that directly on the server, but in that case you wouldn't need plesk at all. So - for many people it is a very big request to add google pagespeed into nginx. If you do not need it: good for you ;-)
Btw., http2 is running perfectly on my plesk-hosted server, you seem to mix something up there.
The comments here about 'We need it now' are rants and useless.
PageSpeed or HTTP/2 integration has nothing to do with Plesk or Parallels. It has to do with support in your webserver. Most Distributions do not yet support HTTP/2.
For example, Debian 8 has no HTTP/2 support in Apache.
It is not Plesk that needs to fix things, you need to wait for a distribution that has support for HTTP/2 and then enable its module.
This topix was started 5 years ago. 3 years ago the admin promised to implement it. NOTHING has happened since then. It has 520 voices already. Please do something FAST!
@admin: what is the status?
Guys! What are you waiting for? Pagemode dir Apache and Ngnix NOW! It ist really about time...
Shane E commented
ngx_pagespeed as standard would be such an improvment
John Shiells commented
caution: adding mod_pagespped breaks websites when NGINX is proxy. you have to turn off static file processing by NGINX.
This is not really a solution Plesk people :) Nginx pagespeed needs to be used instead of the one for Apache.
John Shiells commented
ngx_pagespeed is needed as well!
Daniel Hendricks commented
I would like to see this as well. I would be concerned about static HTM(L) files.
Currently, when mod_pagespeed is enabled in Plesk for Apache, HTM/HTML files come up blank. The recommended fix is to "Serve [htm/html] files directly by nginx" to bypass.
It's pretty ugly as it breaks the default Plesk new web site skeleton pages (most of which have .html extensions). There is nothing like signing up for new hosting and you are greeting with a white page (I fixed it by renaming the .html files to .php and advise users to serve .htm(l) files through nginx, but that's not really a "fix").