• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk Onyx 17.8 Preview

Status
Not open for further replies.
As you remember we postponed 17.8.9 Preview release in December, but now we are in 2018 already and we’ve just published the preview Change Log for Plesk

Killer Feature is Nginx Caching for your site:

View attachment 13899

You will also get Power user mode as default view for new installations. Power user view provides a new on-boarding experience:
(Note: now you are not forced to create a domain to use power user view)

View attachment 13900

You don’t need to install an extension to log in with Google, the extension is shipped and enabled by default:

View attachment 13901

Additional changes:
  • Added support for dist-upgrade to Debian 9.
  • Dropped Tomcat support.
  • Improved experience for Cloud Backups regarding long term operations.
  • PHP engines have been updated to the latest available update.
Just installed Plesk 17.8 on a test VM. I assume this is using proxy_cache. Is data stored in memory or is there a physical path like /data/nginx/cache? We tried to get proxy_cache working last year but were unable to solve permission issues for purges. Would this default install work with WP plugin Nginx Helper or other plugin for purging?

With Varnish we've been using 60 minute cache timeouts. Any reason to not continue using that timeframe?
 
Just installed Plesk 17.8 on a test VM. I assume this is using proxy_cache. Is data stored in memory or is there a physical path like /data/nginx/cache? We tried to get proxy_cache working last year but were unable to solve permission issues for purges. Would this default install work with WP plugin Nginx Helper or other plugin for purging?

With Varnish we've been using 60 minute cache timeouts. Any reason to not continue using that timeframe?

Hello,
when you use proxy_cache you have to add a directive in nginx configuration to set the cache storage path and to make sure nginx will be able to use this cache.

Code:
proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=STATIC:75m inactive=24h max_size=512m;

But to be able to purge nginx cache, it require to compile Nginx with the ngx_cache_purge module, otherwise this feature is only available with Nginx Plus subscription
 
Yea, but this default integration automates all the nginx config. Looks like the cache lives at /var/cache/domain.com_proxy.

Having a WordPress purging mechanism is critical. We can compile Nginx with ngx_cache_purge module easy enough. The problem is that we'd have to take Nginx out the Plesk update tree or every update will erase this. Why is Plesk not shipping this pre-compiled with the purge module? Should be simple enough!
 
Yea, but this default integration automates all the nginx config. Looks like the cache lives at /var/cache/domain.com_proxy.

Having a WordPress purging mechanism is critical. We can compile Nginx with ngx_cache_purge module easy enough. The problem is that we'd have to take Nginx out the Plesk update tree or every update will erase this. Why is Plesk not shipping this pre-compiled with the purge module? Should be simple enough!

It's a third-party module for nginx and there is no guaranty about stability. Plesk cannot add modules from github in their packages.
 
@IgorG we can't recompile Nginx with the purge module because Plesk uses some custom ssl version in its config:

--with-openssl=/home/builder/buildbot/psa-17.8-bcos7x64/build/unix/plesk/packages/nginx/work/openssl-1.0.2n

We'll need the source and there is no public repo. Any solution for us?
 
Will Plesk Onyx 17.8 support TTL for individual DNS records?
As you know, we do not provide any ETA, but it definitely planned "not earlier then H2 2018", because it was not planned to Plesk 17.8 (H1 2018).
 
As you know, we do not provide any ETA, but it definitely planned "not earlier then H2 2018", because it was not planned to Plesk 17.8 (H1 2018).

Thanks for the update, I'm looking forward to finally see this feature in Plesk :)
 
Status
Not open for further replies.
Back
Top