The killing is not something we support aside from console, and at least one other program that someone has made a template for needs a similar thing.
The only real option we have is using kill sadly. I'll look into adding stopping with kill codes in a future version.
Never mind! Changing the auto-restart value to 'true' in the server's config json file seems to have done it. I'll leave this open for a bit to see if anyone has a better answer but that seems to do the trick.
The website was able to connect but this error occurred.
2018/01/15 16:07:04 [alert] 2517#2517: *12 open socket #15 left in connection 5
2018/01/15 16:07:04 [alert] 2517#2517: *11 open socket #14 left in connection 6
2018/01/15 16:07:04 [alert] 2517#2517: aborting
MariaDB 10.1 is fine too. Just add the following lines to the InnoDB section in your mysql .cnf (for me it was /etc/mysql/mariadb.conf.d/50-server.cnf)
# * InnoDB
innodb_file_format = Barracuda
If you edit /etc/apt/sources.list.d/pufferpanel_pufferd.list
you just might be able to get it to install by replacing "zesty" with "xenial"
After you saved your changes, sudo apt update and install it again.
Looks like your connection to PufferPanel Community was lost, please wait while we try to reconnect.