How to definitively isolate multiple Wordpress websites with NginX, HHVM and LetsEncrypt?

I created a droplet in ubuntu 16.04 following the following tutorial and it works like a charm: My goal is to create a shared hosting for my clients projects to replace my current Apache server with PHP-FPM running PHP 5.6 (they will not have access to the server). Searching I did not find a definitive way to isolate the execution of these websites in different users as it is traditionally done by PHP -FPM to increase security. Is this isolation necessary for this scenario? how to do this? Any help is very welcome. Thank you!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I am going to work on this same scenario on a debian 8 install. I intend to follow this -

If your users will have no direct access to the server this step should not be necessary. Should you choose to go forward, this guide seems to have all the bases covered on how to configure PHP-FPM for this type of use-case.

Hi, I finally go it going. You need one hhvm installation and the rest will work. Follow these tuts:

I strongly recommend you use MariaDB instead of MySQL

And the Nginx will look like these FOR EACH SITE. Place the blocks at /etc/nginx/sites-available/default (you can make a copy of default and then delete everything)

#Start of server blocks FOR EACH DOMAIN

# HTTP - redirect all requests to HTTPS:
server {
        listen 80;
        #listen [::]:80 default_server ipv6only=on;
        return 301 https://$server_name$request_uri;

# HTTPS - proxy requests on to wp app:
server {
        listen 443;

        ssl on;
        # Use certificate and key provided by Let's Encrypt:
        ssl_certificate /etc/letsencrypt/live/;
        ssl_certificate_key /etc/letsencrypt/live/;
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

        root /var/www/html/wordpress;
        include hhvm.conf;

        # Add index.php to the list if you are using PHP
        index index.php index.html index.htm index.nginx-debian.html;

        location / {
                try_files $uri $uri/ =404;

        location ~ /favicon.ico {
            access_log off;
            log_not_found off;

        # pass the PHP scripts to FastCGI server listening on sockets

        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                # With php7.0-fpm:
                fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;

        access_log  /var/log/nginx/$host-access.log;
        error_log   /var/log/nginx/wordpress-error.log;


All the best.