Why? The client can work pretty well with the --webroot issue method on any webserver. Hell, if you can take your webserver offline for a short time you can use the --standalone option&#x27;s built in server.<p>Even where you webroot is wired into something else (a proxy, fastcgi, uwsgi&#x2F;django, etc), you can rig it to try to see if a file exists in another directory before handing off.<p><pre><code>    location &#x2F; {
        root &#x2F;web&#x2F;$site&#x2F;webroot;
        try_files $uri $uri&#x2F; @django;
        access_log off;
    }

    location @django {
        include uwsgi_params;
        uwsgi_pass unix:&#x2F;web&#x2F;$site&#x2F;socket;
    }
</code></pre>
Simple! I reuse this in many sites (hence the $site variable) but you could decouple this and use a single directory for all sites&#x2F;certificates (it doesn&#x27;t have to be in the webroot, just something nginx can read).