Appreciated, but with the extra pep talk I should be fine for now. I guess I'll give the new skin a second shot, and it seems like the following lines are all that's needed for routine updates. I agree it's not that cumbersome, since I need to log into the console to do a "yum update" anyway.I will gladly help you with that if you want.
cd /usr/local/directadmin/custombuild
./build update
./build versions
./build update_versions
Doesn't say what the default docroot is, but since all is changing I presume nowadays the new default will be /domain/sub.example.com/public_html insteadl of the old one.here is the change-log entry.
/domain/sub.example.com/public_html
will be offered with an option to use old default /domain/example.com/public_html/sub
or a completely custom path.See if this helps your issueI don't use Roundcube. But DA backup is still trying to export Roundcube, then it leads to error when running backup
Code:RoundCube Backup Error: Fatal error: Uncaught mysqli_sql_exception: Unknown database 'da_roundcube' in /usr/local/directadmin/scripts/backup_roundcube.php:128 Stack trace: #0 /usr/local/directadmin/scripts/backup_roundcube.php(128): mysqli->select_db('da_roundcube') #1 {main} thrown in /usr/local/directadmin/scripts/backup_roundcube.php on line 128
da config-set --restart skip_roundcube_in_backups 1
Try enabling Core functions in tandem with DNS-Only or Email-Only.I setup a new user, with dns-only feature. Use move_domain.sh script for moving in a domain from an existing account on the same server. After that, logging to the new one. Error appears: The request you've made cannot be executed because it does not exist in your authority level. And no other command works, even logout.
Set up a new user, with dns-only feature or email-only feature. The same error.
If switch to core, then DA is working with that new user.
updating to directadmin current v1.647 df8334e9aa47b8f4e98123f3ffac524ab15f86a9 linux_amd64
/usr/local/directadmin/scripts/update.sh:
Another instance of custombuild (PID 1510413) is holding the lock on "/usr/local/directadmin/custombuild/.custombuild.lock", exiting
Sorry to bump this again, but this is not working like this in Enhanced skin. There only the new style subdomain is presented.The subdomains list will just print out the document roots (and PHP versions) that are being used. It will not have any indication for default or non-default values. When creating a subdomain new default value of/domain/sub.example.com/public_html
will be offered with an option to use old default/domain/example.com/public_html/sub
or a completely custom path.