I would like to know if the approach for this would be to create a plugin that gives the user access to that plugin, which in and of itself would be a restricted panel and that plugin would be like "websites" but isolated to /srv/http/thisusersite (controlled by a higher power) somehow. If anyone thinks this is a valid scheme I will pursue, but if it's not would like input on alternative approaches.

Know of anyone working on this concept here or elsewhere? It's a great idea.

Based on the above it would be for the PHP .ini values in the FastCGI of the content section:

open_basedir = /srv/webroot/of/this/site:/tmp;

Fixed in config.inc.php

$cfg['ForceSSL'] = true;

I think Eugene (re)wrote it so that a value of "none" is to be inserted: open_basedir = none (which is better than empty) but for a set up like mine with many WordPress installs the folder location is the preferred solution. This is discussed elsewhere in here, Eugeny github and probably stackexchange too.

The FastCGI is not invoked automatically because sites that are not php based will require parameters for node.js, Python etc... I follow the WordPress procedures prescribed by Ajenti by Myles here on a WordsRack Nginx hardened set up.

In the websites section of ajenti -v you have PHP FastCGI section built?

If so, you put in, according to your file structure for PHP .ini values - like: open_basedir = /srv/http/0002:/tmp

Installation on my sub domain works good..... except at initial login the url is appended with port /:80 and I don't want this since I am resolving good on https/ssl.

When I first login the url is forced to be like this:

`https://pma.mydomain.com:80/index.php?token=xxxxxxxxxxx`

And page says "SSL Connection error"

So I go to `https://pma.mydomain.com` in same browser and I am logged in and working perfectly.

Searching in docs cannot find where I may control this behaviour.

thx

I apologize if this is not in the right area. If I should raise a new topic this can be deleted.