Search results

tmp_table_size = 256M max_heap_table_size = 256M table_definition_cache = 10000 key_buffer_size = 32M innodb_buffer_pool_size = 6G innodb_log_file_size should be = 256M

you can run mysqltuner to check if your mysql config optimal and what you can optimize. also you can enable opcache - it helps with WP too.

On your screen only one core loaded to 85% all other free. Total load about 5% On linux systems 100% process usage shows 1 fully loaded core, so sometimes you can see 800% and other digits that show you that this process using 8 cores now. At higher part you see your cores/threads 0-11 - total...

check email rating in https://www.mail-tester.com then just fix described problems. for good emailing you must have properly configured: rDNS, SPF, DKIM, DMARC, MX, unsubscribe link.

+1 for Almalinux 9 and fresh php, as you will install few versions on server - better to set as main currently stable that will be supported at least 1+ year more, so 8.2 or 8.3

usually it takes 2-3 months, also 24.04 to raw and has some bugs, I recommend wait till 24.04.1

try add caldav.domain.com as separate domain and issue cert for it separately

I know that I can swap IP with perl/sed script after restore, but I thought it can be done some DA-native way.

Hello, When I move users from one DA server to another with DA-backup - it replaces A-records only for subdomains which has only one A-record. In my case at old server I domains have 5 A-records with different ips: domain IN A 12.12.12.11 domain IN A 13.12.12.12 domain IN A 14.12.12.13 domain...

can you add supporting of old and new backups for restore from DA: Invalid filename: user.reseller.agro.tar.zst. The file must be of the form: username.tar.gz my bad, it was name issue, but check also extension support, I already recreated backups as tar.gz and don't have zst to test.

also when we bought our licenses mariadb didn't exist - but they implemented it, they implemented each LTS mysql 5.5, 5.6, 5.7, 8 maria 5.5, 10, 10.1 - 10.6 - all they was separate LTS branches and was integrated with DA without issues, now they decided to change rules :mad: It was same 10 years...

here how it looks inside DNS .db file

you can divide it to parts separated with doublequotes "code1""code2""code3"

update your OS packages and Directadmin to latest versions. It can't be freshly installed because tries to install old PHP version, maybe you installed it from VPS template with outdated Directadmin inside?

same after updating to 1.660 - they told it outdated browser (2+ years mine, old OS can't update). I changed skin to enhanced by editing user's conf.

it's outdated DA, they changed a lot since this 1,5 years, you need to update DA and OS packages to latest stable.

@xar123 https://endoflife.date/mariadb you are using EOL version, try upgrade to 10.4->10.5->10.6

@floyd PHP.net maintains 3 versions in same time. Old one, current stable, newest one. Usually lifetime 3 years (32-40 releases).

have you checked mysql status from console? logs?

https://docs.directadmin.com/changelog/version-1.50.0.html#let-s-encrypt-automated-free-ssl-certificate-installs-skins-lang There is an internal variable, set by default to: letsencrypt_renewal_days=85 Check if it really same in your case, or you have old setting about 60 days.