Search results

Hello, if you need to update ioncube loader, here the steps to follow : Example for php7.0 # find the php extension dir /opt/plesk/php/7.0/bin/php -i | grep extension_dir # download ioncube laoders wget http://downloads3.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.zip unzip...

Hello, you have to enable your firewall to block direct access to your container on the custom ports you have choosen. Otherwise, you docker container will always be accessible directy, even with http://YOUR-SERVER-IP:XXXX

New release available. Changelog : latest nginx mainline release : v1.13.12 revert ngx_brotli to the previous version due to issues @IgorG I have no idea of the reason, but I'm not able to download the latest version of your script. The button "download" link to the first release with nginx...

We are still running tests on renewal process, because acme.sh renew automatically all certificates every 30 days, and it provide the ability to reload nginx and apache after the renewal. But we haven't find the best way to update wildcard certs added in Plesk yet. I think it's only related to...

Hello @learning_curve, at the moment, we use acme.sh (with Cloudflare DNS) to issue Let's Encrypt wildcard certificates, and the Plesk CLI to add them in Plesk. Steps to setup our certificates : # issue a wildcard ECC ceritficate with Cloudflare DNS API validation acme.sh --issue -d...

New release available. Changelog : Github page : Plesk Nginx update nginx : v1.13.10 update brotli : v1.0.2

Hello, we have to wait for the next stable openssl release ; v1.1.1

There was too many draft releases of TLS v1.3, and the most part of them cannot be enabled in web browser even in hidden settings like chrome://flags : But about Brotli, I was already using ngx_brotli in my bash script, and I have noticed there was no updates since August 2016. In fact...

Yes : :authority: XXX.xyz :method: GET :path: / :scheme: https accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8 accept-encoding: gzip, deflate, br accept-language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7 cache-control: max-age=0 cookie...

I have tried with the same settings and cache status is always BYPASS content-encoding: br content-type: text/html; charset=UTF-8 date: Wed, 21 Mar 2018 10:18:41 GMT link: <https://XXX.xyz/index.php/wp-json/>; rel="https://api.w.org/", <https://XXX.xyz/>; rel=shortlink ms-author-via: DAV...

Hello, no_cache directive is added in your vhost configuration when you enable micro-caching on a website. Try to disable Nginx micro-cache configuration files are located in /etc/nginx/plesk.d/vhosts but are automatically regenerated by Plesk.

Nginx cache configuration can be easily customized : Enabling nginx caching Apache and Nginx Settings Plesk 17.8 is a major update on performance, especially for the Plesk web interface. But Nginx cache cannot be (fully) automatically configured & optimized by Plesk. For example, the static...

Hello, your emails seems to be reject by gmail because some configuration are not correct for a mail server. - Your server hostname have to be a FQDN (Fully qualified domain name) like server.yourdomain.tld and not only yourdomain.tld - You have to set the server hostname as reverse DNS on...

Nginx proxy_cache can be used to do serve static content from another upstream. I'm using it on my blogs running with Ghost but it require to exclude all URLs you do not want to cache or to use cookies to bypass the cache. Otherwise, Nginx will directly serve cache content until it expire. Here...

The main purpose of microcaching is to reduce downtime by serving cache each time the next upstream is down. So in case of high-traffic, if Apache timeout or isn't able to answer to a request, Nginx will use micro-caching instead of displaying a 502 Bad Gateway. During Let's Encrypt renewal, it...

Hello, With micro-caching, Nginx only serve cache if the next upstream (Apache) is down. It provide a way to avoid error 502 bad gateway but it doesn't server a static version of your website if Apache is running properly. Yes, micro-caching is a new feature available on Plesk 17.8

Ok, I was not sure to understand the reason of using SAN. So, to answer to your question, you can use your SAN SSL certificate to secure Plesk interface and your mail server, and use your wildcard cert in your wildcard cert in your subscription to secure your website. Just make sure to set the...

Hello, if you have a wildcard certificate for your domain, why would you use another certificate to secure Plesk interface and mail server ? You can use the wildcard certificate to secure your website and Plesk/mail server. When you add a SSL certificate into a subscription, you can also use...

My servers running with Plesk 17.8.11 are shipped with Nginx 1.13.8 by default, so it's almost the last release available. Here the Nginx -V : nginx version: nginx/1.13.8 built with OpenSSL 1.0.2g 1 Mar 2016 TLS SNI support enabled configure arguments: --prefix=/usr/share...

Scripts written by @IgorG or me only compile and replace the Nginx package shipped with Plesk. It will install usual packages needed to build a program from source, and required dev-libraries, but nothing directly related to Plesk. The most part of my servers are running with Plesk 17.8.11 and...