Hi Stu,

Ajenti doesn't affect your ability to use SSH pubkey auth. However, if you deleted and recreated user, it's possible that their authorized_keys file was lost. Try looking for the <user home>/.ssh/authorized_keys file and checking whether your public key is present there.

If you already have "/" location in Content, put your location settings into Content > (content entry) > Advanced > Custom configuration instead.

"Edit" button will be available in the properties dialog

Hello, you can use existing simple plugins such as Hosts as examples, and also refer to examples from documentation. Mail me at e@ajenti.org if you run into problems.

https://github.com/python-greenlet/greenlet/issues/25#issuecomment-12858145 suggests that it was fixed in recent Ubuntu update. Make sure that you a) have updates repo enabled and b) upgrade all Python-related packages to latest versions.

It's pretty easy. Actually you can configure that "proxying" website from ajenti-v too. Simply create multiple locations (per "child" website) in it, of type "Reverse proxy" and set their URLs to http://127.0.0.1:<child-port> (and don't forget to set desired url pattern).